Out of interest how to do you guys represent NUMA regions of memory in
the device tree?
- k
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.
Jon
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
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