From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Wed, 15 Nov 2006 14:40:36 -0800 (PST) From: Christoph Lameter Subject: Re: [patch 2/2] enables booting a NUMA system where some nodes have no memory In-Reply-To: <20061115215845.GB20526@sgi.com> Message-ID: References: <20061115193049.3457b44c@localhost> <20061115193437.25cdc371@localhost> <20061115215845.GB20526@sgi.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-mm@kvack.org Return-Path: To: Jack Steiner Cc: Christian Krafft , linux-mm@kvack.org, Martin Bligh , linux-kernel@vger.kernel.org List-ID: On Wed, 15 Nov 2006, Jack Steiner wrote: > A lot of the core infrastructure is currently missing that is required > to describe IO nodes as regular nodes, but in principle, I don't > see anything wrong with nodes w/o memory. Every processor has a local node on which it runs. The kernel places memory used by the processor on the local node. Even if we allow nodes without memory: We still need to associate a "local" node to the processor. If that is across some NUMA interlink then it is going to be slower but it will work. AFAIK It seems to be better to explicitly associate a memory node with a processor during bootup in arch code. Various kernel optimizations rely on local memory. Would we create a special case here of a pglist_data structure without a zones structure? It seems that the contents of pglist_data are targeted to a memory node. If we do not have a pglist_data structure then the node would not exist for the kernel. What would the benefit or difference be of having nodes without memory? -- 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: email@kvack.org