linux-kernel - Re: [PATCH] properly reserve in bootmem the lmb reserved regions that cross numa nodes

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1DA7FAFA-0708-4CFC-B721-B09A29F45B3F@kernel.crashing.org>
Date:	Mon, 6 Oct 2008 10:58:25 -0500
From:	Kumar Gala <galak@...nel.crashing.org>
To:	Jon Tollefson <kniht@...ux.vnet.ibm.com>
Cc:	Adam Litke <agl@...ibm.com>,
	linuxppc-dev <linuxppc-dev@...abs.org>,
	Adam Litke <agl@...ux.vnet.ibm.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Linux Memory Management List <linux-mm@...ck.org>
Subject: Re: [PATCH] properly reserve in bootmem the lmb reserved regions that cross numa nodes


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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/