public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Martin J. Bligh" <mbligh@aracnet.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Dave Hansen <haveblue@us.ibm.com>, linux-kernel@vger.kernel.org
Subject: Re: kexec reboot code buffer
Date: Wed, 29 Jan 2003 08:17:44 -0800	[thread overview]
Message-ID: <1947260000.1043857063@titus> (raw)
In-Reply-To: <m165s855fr.fsf@frodo.biederman.org>

>> > I am fine with memory that is not physically contiguous.  The memory
>> > I really want the kernel is currently sitting on.....
>> 
>> Oh, in that case you should have no problem getting it from ZONE_NORMAL,
>> especially if you can wake up kswapd and wait for a few seconds.
> 
> Nope, kswapd will not free the kernels text segment.  So in practice
> I can use anything below 4GB. 

Oh, I'm well aware that the kernel won't get swapped out ;-) 
I was referring to the getting memory that's "not physically contiguous"
by waking up kswapd ;-)

> There is even a distribution built to be run completely out of a ramdisk. 
> http://warewulf-cluster.org/

Terrifying ;-)
  

M.


  reply	other threads:[~2003-01-29 16:08 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3E31AC58.2020802@us.ibm.com>
2003-01-25 14:16 ` kexec reboot code buffer Eric W. Biederman
2003-01-27 21:55   ` Dave Hansen
2003-01-27 22:03     ` Martin J. Bligh
2003-01-28  0:10       ` William Lee Irwin III
2003-01-28  7:24       ` Eric W. Biederman
2003-01-28 16:15         ` Martin J. Bligh
2003-01-29 15:41           ` Eric W. Biederman
2003-01-29 16:17             ` Martin J. Bligh [this message]
2003-01-28  7:04     ` Eric W. Biederman
2003-01-28  7:18       ` William Lee Irwin III
2003-01-28  7:28         ` Eric W. Biederman
2003-01-28  7:31           ` William Lee Irwin III
2003-01-28 15:21             ` Eric W. Biederman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1947260000.1043857063@titus \
    --to=mbligh@aracnet.com \
    --cc=ebiederm@xmission.com \
    --cc=haveblue@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox