From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Robert Picco <Robert.Picco@hp.com>
Cc: Jesse Barnes <jbarnes@sgi.com>,
linux-kernel@vger.kernel.org, colpatch@us.ibm.com,
haveblue@us.ibm.com
Subject: Re: boot time node and memory limit options
Date: Wed, 17 Mar 2004 12:58:09 -0800 [thread overview]
Message-ID: <3580000.1079557089@flay> (raw)
In-Reply-To: <4058AE91.8000909@hp.com>
>> Yes ... that's looking very 2.7-ish to reorganise all that stuff. However,
>> for now, I still think we need to restrict memory very early on, before
>> anything else can allocate bootmem. Are you the absolute first thing that
>> ever runs in the boot allocator?
>>
>> M.
>>
>>
> All the machine dependent initialization code could have allocated and/or reserved bootmem before the patch would claim additional memory based on boot line parameters. The patch is called just before mem_init. There aren't any pages on freelist yet because mem_init hasn't been called. So I'm not the first thing that ever runs in the boot allocator. I'm not sure that my answer is addressing your question?
You are, but it's not the answer I want ;-) If you can allocate stuff out
of bootmem that should have been barred by the limiter, I think that's
a bad idea ... you should be restricting earlier, IMHO.
M.
next prev parent reply other threads:[~2004-03-17 20:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4057392A.8000602@hp.com>
2004-03-16 17:43 ` boot time node and memory limit options Jesse Barnes
2004-03-16 19:39 ` Martin J. Bligh
2004-03-17 16:15 ` Robert Picco
2004-03-17 16:36 ` Martin J. Bligh
2004-03-17 17:09 ` Dave Hansen
2004-03-17 17:51 ` Jesse Barnes
2004-03-17 18:12 ` Dave Hansen
2004-03-17 19:30 ` Robert Picco
2004-03-17 19:44 ` Martin J. Bligh
2004-03-17 20:01 ` Robert Picco
2004-03-17 20:58 ` Martin J. Bligh [this message]
2004-03-17 20:52 ` Dave Hansen
2004-03-16 17:07 Robert Picco
2004-03-16 17:34 ` Randy.Dunlap
[not found] ` <16471.48076.447058.132559@napali.hpl.hp.com>
2004-03-17 18:07 ` Robert Picco
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=3580000.1079557089@flay \
--to=mbligh@aracnet.com \
--cc=Robert.Picco@hp.com \
--cc=colpatch@us.ibm.com \
--cc=haveblue@us.ibm.com \
--cc=jbarnes@sgi.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