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 09:11:59 -0800 [thread overview]
Message-ID: <1100711519.5838.2.camel@localhost> (raw)
In-Reply-To: <1100659057.26335.125.camel@knk>
On Tue, 2004-11-16 at 18:37, keith wrote:
> The numa KVA code used the node_start and node_end values (obtained
> from the above memory ranges) to make it's lowmem reservations. The
> problem is that the lowmem area reserved is quite large. It reserves
> the entire a lmem_map large enough for 0x1000000 address space. I don't
> feel this is a great use of lowmem on my system :)
It does seem silly to waste all of that lowmem for memory that *might*
be there, but what do you plan to do for contiguous address space (for
mem_map) once the memory addition occurs? We've always talked about
having to preallocate mem_map space on 32-bit platforms and by your
patch it appears that this isn't what you want to do.
-- 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-17 17:12 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 ` Dave Hansen [this message]
2004-11-18 2:08 ` [Lhms-devel] " keith
2004-11-18 2:24 ` Dave Hansen
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=1100711519.5838.2.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