On Wed, 2005-09-07 at 11:22 -0700, Martin J. Bligh wrote:
> 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.
-- Dave
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
| |
 |