Thread (13 messages) 13 messages, 5 authors, 2005-09-08

Re: [PATCH] i386: single node SPARSEMEM fix

From: Magnus Damm <magnus.damm@gmail.com>
Date: 2005-09-08 01:51:14
Also in: lkml

On 9/8/05, Dave Hansen [off-list ref] wrote:
On Wed, 2005-09-07 at 11:22 -0700, Martin J. Bligh wrote:
quoted
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.
Actually, I do not really care about the Kconfig stuff. I just added
that to show you guys why and when the change in
arch/i386/kernel/setup.c was needed. So my main interest is to include
the fix to the single-node version of setup_memory(). This to sync up
the single-node case with the multiple-node version of setup_memory(),
and to make it easier for me and other people to start using sparsemem
om single-node (or non-NUMA if you prefer that) configurations.

/ magnus
--
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:"dont@kvack.org"> email@kvack.org </a>
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help