From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from e2.ny.us.ibm.com (e2.ny.us.ibm.com [32.97.182.142]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "e2.ny.us.ibm.com", Issuer "Equifax" (verified OK)) by ozlabs.org (Postfix) with ESMTPS id 623E8DDF39 for ; Tue, 7 Oct 2008 07:48:26 +1100 (EST) Received: from d01relay02.pok.ibm.com (d01relay02.pok.ibm.com [9.56.227.234]) by e2.ny.us.ibm.com (8.13.8/8.13.8) with ESMTP id m96KmMQs008498 for ; Mon, 6 Oct 2008 16:48:22 -0400 Received: from d01av04.pok.ibm.com (d01av04.pok.ibm.com [9.56.224.64]) by d01relay02.pok.ibm.com (8.13.8/8.13.8/NCO v9.1) with ESMTP id m96KmM8E284632 for ; Mon, 6 Oct 2008 16:48:22 -0400 Received: from d01av04.pok.ibm.com (loopback [127.0.0.1]) by d01av04.pok.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id m96KmCcO018240 for ; Mon, 6 Oct 2008 16:48:12 -0400 Message-ID: <48EA79AC.8090705@linux.vnet.ibm.com> Date: Mon, 06 Oct 2008 15:48:44 -0500 From: Jon Tollefson MIME-Version: 1.0 To: Kumar Gala Subject: Re: [PATCH] properly reserve in bootmem the lmb reserved regions that cross numa nodes References: <48E23D6C.4030406@linux.vnet.ibm.com> <1222789675.13978.14.camel@localhost.localdomain> <7E5B6DFB-F9DE-4929-8A4F-8011BF817017@kernel.crashing.org> <48EA31D5.70609@linux.vnet.ibm.com> <1DA7FAFA-0708-4CFC-B721-B09A29F45B3F@kernel.crashing.org> In-Reply-To: <1DA7FAFA-0708-4CFC-B721-B09A29F45B3F@kernel.crashing.org> Content-Type: text/plain; charset=ISO-8859-1 Cc: Linux Memory Management List , linuxppc-dev , Adam Litke , Linux Kernel Mailing List List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Kumar Gala wrote: > > On Oct 6, 2008, at 10:42 AM, Jon Tollefson wrote: > >> Kumar Gala wrote: >>> Out of interest how to do you guys represent NUMA regions of memory in >>> the device tree? >>> >>> - k >> Looking at the source code in numa.c I see at the start of >> do_init_bootmem() that parse_numa_properties() is called. It appears to >> be looking at memory nodes and getting the node id from it. It gets an >> associativity property for the memory node and indexes that array with a >> 'min_common_depth' value to get the node id. >> >> This node id is then used to setup the active ranges in the >> early_node_map[]. >> >> Is this what you are asking about? There are others I am sure who know >> more about it then I though. > > I was wondering if this was documented anywhere (like in sPAPR)? > > - k I see some information on it in section "C.6.6". Jon