From: "Martin J. Bligh" <mbligh@mbligh.org>
To: Andrew Morton <akpm@osdl.org>
Cc: haveblue@us.ibm.com, magnus@valinux.co.jp,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
andyw@uk.ibm.com
Subject: Re: [PATCH] i386: single node SPARSEMEM fix
Date: Wed, 07 Sep 2005 23:11:29 -0700 [thread overview]
Message-ID: <40650000.1126159888@[10.10.2.4]> (raw)
In-Reply-To: <20050907164945.14aba736.akpm@osdl.org>
>> >> CONFIG_NUMA was meant to (and did at one point) support both NUMA and flat
>> >> machines. This is essential in order for the distros to support it - same
>> >> will go for sparsemem.
>> >
>> > That's a different issue. The current code works if you boot a NUMA=y
>> > SPARSEMEM=y machine with a single node. The current Kconfig options
>> > also enforce that SPARSEMEM depends on NUMA on i386.
>> >
>> > Magnus would like to enable SPARSEMEM=y while CONFIG_NUMA=n. That
>> > requires some Kconfig changes, as well as an extra memory present call.
>> > I'm questioning why we need to do that when we could never do
>> > DISCONTIG=y while NUMA=n on i386.
>>
>> Ah, OK - makes more sense. However, some machines do have large holes
>> in e820 map setups - is not really critical, more of an efficiency
>> thing.
>
> Confused. Does all this mean that we want the patch, or not?
>From that POV, nothing urgent, and would require more work to make use
of it anyway. Not sure if Magnus had another more immediate use for it?
M.
next prev parent reply other threads:[~2005-09-08 6:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-06 3:56 Magnus Damm
2005-09-07 17:28 ` Dave Hansen
2005-09-07 18:22 ` Martin J. Bligh
2005-09-07 18:27 ` Dave Hansen
2005-09-07 18:34 ` Martin J. Bligh
2005-09-07 23:49 ` Andrew Morton
2005-09-08 0:46 ` Dave Hansen
2005-09-08 1:54 ` Magnus Damm
2005-09-08 6:11 ` Martin J. Bligh [this message]
2005-09-08 6:36 ` Magnus Damm
2005-09-08 1:51 ` Magnus Damm
2005-09-08 1:45 ` Magnus Damm
2005-09-08 1:40 ` Magnus Damm
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='40650000.1126159888@[10.10.2.4]' \
--to=mbligh@mbligh.org \
--cc=akpm@osdl.org \
--cc=andyw@uk.ibm.com \
--cc=haveblue@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=magnus@valinux.co.jp \
/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
all inboxes | Powered by JetHome®