From: Kumar Gala <galak@kernel.crashing.org>
To: Jon Tollefson <kniht@linux.vnet.ibm.com>
Cc: Adam Litke <agl@us.ibm.com>,
linuxppc-dev <linuxppc-dev@ozlabs.org>,
Adam Litke <agl@linux.vnet.ibm.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [PATCH] properly reserve in bootmem the lmb reserved regions that cross numa nodes
Date: Mon, 6 Oct 2008 10:58:25 -0500 [thread overview]
Message-ID: <1DA7FAFA-0708-4CFC-B721-B09A29F45B3F@kernel.crashing.org> (raw)
In-Reply-To: <48EA31D5.70609@linux.vnet.ibm.com>
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
next prev parent reply other threads:[~2008-10-06 16:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-30 14:53 Jon Tollefson
2008-09-30 15:47 ` Adam Litke
2008-10-01 21:02 ` Kumar Gala
2008-10-06 15:42 ` Jon Tollefson
2008-10-06 15:58 ` Kumar Gala [this message]
2008-10-06 20:48 ` Jon Tollefson
2008-10-02 21:52 ` Jon Tollefson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1DA7FAFA-0708-4CFC-B721-B09A29F45B3F@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--cc=agl@linux.vnet.ibm.com \
--cc=agl@us.ibm.com \
--cc=kniht@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®