From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Fri, 13 May 2005 04:33:11 -0700 From: Andrew Morton Subject: Re: NUMA aware slab allocator V2 Message-Id: <20050513043311.7961e694.akpm@osdl.org> In-Reply-To: References: <20050512000444.641f44a9.akpm@osdl.org> <20050513000648.7d341710.akpm@osdl.org> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org Return-Path: To: Christoph Lameter Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org, shai@scalex86.org, steiner@sgi.com List-ID: Christoph Lameter wrote: > > On Fri, 13 May 2005, Andrew Morton wrote: > > > It didn't produce anything interesting. For some reason the console output > > stops when start_kernel() runs console_init() (I guess it all comes out > > later) so the machine is running blind when we run kmem_cache_init(). > > Irritating. I just moved the console_init() call to happen later on. > > > > It's going BUG() in kmem_cache_init()->set_up_list3s->is_node_online > > because for some reason the !CONFIG_NUMA ppc build has MAX_NUMNODES=16, > > even though there's only one node. > > Yuck. > > The definition for the number of NUMA nodes is dependent on > CONFIG_FLATMEM instead of CONFIG_NUMA in mm. > CONFIG_FLATMEM is not set on ppc64 because CONFIG_DISCONTIG is set! And > consequently nodes exist in a non NUMA config. I was testing 2.6.12-rc4 base. -- 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: aart@kvack.org