Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262363AbVEMNqh (ORCPT ); Fri, 13 May 2005 09:46:37 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262364AbVEMNqh (ORCPT ); Fri, 13 May 2005 09:46:37 -0400 Received: from e1.ny.us.ibm.com ([32.97.182.141]:14785 "EHLO e1.ny.us.ibm.com") by vger.kernel.org with ESMTP id S262363AbVEMNqf (ORCPT ); Fri, 13 May 2005 09:46:35 -0400 Subject: Re: NUMA aware slab allocator V2 From: Dave Hansen To: Christoph Lameter Cc: Andrew Morton , linux-mm , Linux Kernel Mailing List , shai@scalex86.org, steiner@sgi.com In-Reply-To: References: <20050512000444.641f44a9.akpm@osdl.org> <20050513000648.7d341710.akpm@osdl.org> Content-Type: text/plain Date: Fri, 13 May 2005 06:46:17 -0700 Message-Id: <1115991978.7129.3.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.0.4 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 842 Lines: 22 On Fri, 2005-05-13 at 04:21 -0700, Christoph Lameter wrote: > 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. > > s/CONFIG_NUMA/CONFIG_FLATMEM/ ?? FLATMEM effectively means that you have a contiguous, single mem_map[]; it isn't directly related to NUMA. Could you point me to the code that you're looking at? We shouldn't have numbers of NUMA nodes is dependent on CONFIG_FLATMEM, at least directly. -- Dave - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/