[Top] [All Lists]

Q: vailable memory when initrd exists?

Subject: Q: vailable memory when initrd exists?
From: "Y Yang" <>
Date: Wed, 23 May 2007 21:31:41 -0700
Dkim-signature: a=rsa-sha1; c=relaxed/relaxed;; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=b9kfEOJ5Q6hosw2H8aOQwtoorEdYUwE82vfSo/OY7U9Jdqg+bY/sKxg57l6x1vMPvroV9R51ep3Ypm0jQ2z7Rd/MPqEx+cFLqPLLfvgIgPSYxSdEobxT/JIoBbSoUXUOh+50AxNjlKUmZzErhVvmpCt7ymDQzSe9D9g44+Edj68=
Domainkey-signature: a=rsa-sha1; c=nofws;; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=KVJlkmhHNvQcV/qiilFbM3z93PLOdcFPK0bwwaEif0Ebbx7zqvwHv4xP3hyb0Zs78Xxa4LmTon8xgt96ZIeGHEcqgge5RE83nOQtjrtumZ/W7N/jnKzBxDv6YHab5mYl34pUSRP1BV/LBpLJ9WC8utTdt+PJlPmn01h00ym6xv8=
Original-recipient: rfc822;
In "arch/mips/kernel/setup.c", it appears that the "free memory" pool
is the memory area after kernel code and initrd if configured. Since
the location of "initrd" is set by "rd_start", it is possible that
there will be "memory hole" between the kernel and "initrd". It is my
understanding that the memory area up to the "free memory" pool will
not be available, even after "initrd" is freed later in the boot
process. I am curious as why it is necessary to do it this way? What
if we treat the whole area after the kernel code as the "free memory"
pool? This shouldn't affect "initrd", as the memory used by "initrd"
is reserved.

I looked at both older 2.6.14 and the latest kernel code. That part of
the logic seems largely unchanged. I suspect I must have missed

Thanks for your help in advance.



<Prev in Thread] Current Thread [Next in Thread>
  • Q: vailable memory when initrd exists?, Y Yang <=