From: Dave Hansen <haveblue@us.ibm.com>
To: keith <kmannth@us.ibm.com>
Cc: external hotplug mem list <lhms-devel@lists.sourceforge.net>,
linux-mm <linux-mm@kvack.org>, Chris McDermott <lcm@us.ibm.com>
Subject: Re: [Lhms-devel] [RFC] fix for hot-add enabled SRAT/BIOS and numa KVA areas
Date: Wed, 17 Nov 2004 18:24:04 -0800 [thread overview]
Message-ID: <1100744644.17510.8.camel@localhost> (raw)
In-Reply-To: <1100743722.26335.644.camel@knk>
On Wed, 2004-11-17 at 18:08, keith wrote:
> I am not anticipating to support hot-add without config_nonlinear or
> something similar which should provide more flexibility in allocation of
> smaller section mem_maps. This is only a issue when booted as a
> discontig system. We don't even consult the SRAT when we boot flat
> (contiguous address space) so it is a non-issue.
Once a system has been running for any length of time, finding any
multi-order pages gets somewhat hard. For a 16M section, you're still
talking about ~128k of mem_map, which is still an order 5 allocation.
Nick's kswapd higher-order patches should help with this, though.
> Wasting 500k of lowmem for memory that "might" be there is no good. I
> don't think having to preallocate the mem_map for a hot-add is really
> that good. What if the system never adds memory? What if it only adds
> 8gig not 49g? The system is crippled because it reserves the lmem_map
> it "might" do a hot add with?
I have the feeling we'll eventually need a boot-time option for this
reservation. Your patch, of course will work for now. Do you want me
to pick it up in my tree?
> I forgot the mention that without this patch my system does not boot
> with the hot-add support enabled in the bios.
Why not? I'm just curious what caused the actual failure.
-- Dave
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2004-11-18 2:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-17 2:37 keith
2004-11-17 17:11 ` [Lhms-devel] " Dave Hansen
2004-11-18 2:08 ` keith
2004-11-18 2:24 ` Dave Hansen [this message]
2004-11-18 19:18 ` keith
2004-11-17 22:33 ` Yasunori Goto
2004-11-17 22:42 ` Dave Hansen
2004-11-17 23:21 ` Yasunori Goto
2004-11-18 2:18 ` keith
2004-11-18 2:16 ` keith
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=1100744644.17510.8.camel@localhost \
--to=haveblue@us.ibm.com \
--cc=kmannth@us.ibm.com \
--cc=lcm@us.ibm.com \
--cc=lhms-devel@lists.sourceforge.net \
--cc=linux-mm@kvack.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