Re: NODE_DATA without CONFIG_NUMA

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, 4 Sep 2006, Jes Sorensen wrote:

> Christoph Lameter wrote:
> > On Mon, 4 Sep 2006, Jes Sorensen wrote:
> > 
> > > I haven't looked at the details, given you don't say where it breaks,
> > > but it would make sense to me that a non-NUMA system is treated as a
> > > single node system, eg. NODE_DATA(0) ought to be valid.
> > 
> > NODE_DATA should always be available. The problem is likely due to DISCONTIG
> > being associatiated tightly with NUMA.
> 
> But DISCONTIG will probably go away at some point, so maybe it's time to
> disentangle that?

I think we should fix the bug.

Disentangle is good but we cannot get rid of DISCONTIG since SPARSEMEM so 
far does not match DISCONTIG performance since it does not support 
virtual mem_map. See the recent discussion in regards to virt_to_page().

-
To unsubscribe from this list: send the line "unsubscribe linux-ia64" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel]     [Sparc Linux]     [DCCP]     [Linux ARM]     [Yosemite News]     [Linux SCSI]     [Linux x86_64]     [Linux for Ham Radio]

  Powered by Linux