public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Dave Hansen <haveblue@us.ibm.com>,
	"Eric W. Biederman" <ebiederm@xmission.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kexec reboot code buffer
Date: Mon, 27 Jan 2003 14:03:24 -0800	[thread overview]
Message-ID: <203100000.1043705004@flay> (raw)
In-Reply-To: <3E35AAE4.10204@us.ibm.com>

>> The problem is that I have not figured out how to tell the memory
>> allocator just what I need, 
> <snip>
>> I guess I would make the standard zones something like:
>> /*
>>  * ZONE_DMA	  < 16 MB	ISA DMA capable memory
>>  * ZONE_NORMAL  16-896 MB	direct mapped by the kernel
>>  * ZONE_PHYSMEM 896-4096 MB	memory that is accessible with the
>>                               MMU disabled.
>>  * ZONE_HIGHMEM > 4096MB      only page cache and user processes
>>  */
> 
> I think this might be overkill.  ZONE_NORMAL gives you what you want,
> and I don't think it's worth it to introduce a new one just for the
> relatively short timespan where you have the new kernel loaded, but
> haven't actually shut down.  I think a little comment next to the
> allocation explaining this will be more than enough.
> 
> Martin, any ideas?

We talked about creating a new zone specifically for DMA32 (ie <4Gb)
for other reasons, but it's not there as yet. As Dave mentioned,
ZONE_NORMAL should be sufficient, though if you need it physically
contiguous, that might be a problem.

How much memory do you need? If it's only 2Mb or so, why don't we
statically reserve it at boot time and keep it set aside?

M.


  reply	other threads:[~2003-01-27 22:02 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 [this message]
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
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=203100000.1043705004@flay \
    --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