From: Dave Hansen <haveblue@us.ibm.com>
To: Zou Nan hai <nanhai.zou@intel.com>
Cc: LKML <linux-kernel@vger.kernel.org>, Suresh.b.siddha@intel.com
Subject: Re: [Patch] Allocate sparse vmemmap block above 4G
Date: Wed, 07 Nov 2007 09:12:30 -0800 [thread overview]
Message-ID: <1194455550.7078.58.camel@localhost> (raw)
In-Reply-To: <1194419267.3046.1412.camel@linux-znh>
On Wed, 2007-11-07 at 15:07 +0800, Zou Nan hai wrote:
> Try to allocate sparse vmemmap block above 4G on x64 system.
>
> On some single node x64 system with huge amount of physical memory e.g
> 64G. the memmap size maybe very big.
Could we just change the default bootmem behavior to allocate top-down?
-- Dave
next prev parent reply other threads:[~2007-11-07 17:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-07 7:07 [Patch] Allocate sparse vmemmap block above 4G Zou Nan hai
2007-11-07 17:12 ` Dave Hansen [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-11-08 0:52 Zou Nan hai
2007-11-08 14:07 ` Mel Gorman
2007-11-09 1:28 ` Zou, Nanhai
2007-11-09 1:54 ` Christoph Lameter
2007-11-09 14:42 ` Mel Gorman
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=1194455550.7078.58.camel@localhost \
--to=haveblue@us.ibm.com \
--cc=Suresh.b.siddha@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nanhai.zou@intel.com \
/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