On Thu, 2016-13-10 at 05:27:30 UTC, Michael Ellerman wrote:
> At boot we dump the NUMA memory topology in dump_numa_memory_topology(),
> at KERN_DEBUG level, resulting in output like:
>
> Node 0 Memory: 0x0-0x1
> Node 1 Memory: 0x1-0x2
>
> Which is nice enough, but imm
Balbir Singh writes:
> On 13/10/16 16:27, Michael Ellerman wrote:
>> At boot we dump the NUMA memory topology in dump_numa_memory_topology(),
>> at KERN_DEBUG level, resulting in output like:
>>
>> Node 0 Memory: 0x0-0x1
>> Node 1 Memory: 0x1-0x2
>>
>> Which is nice
On 13/10/16 16:27, Michael Ellerman wrote:
> At boot we dump the NUMA memory topology in dump_numa_memory_topology(),
> at KERN_DEBUG level, resulting in output like:
>
> Node 0 Memory: 0x0-0x1
> Node 1 Memory: 0x1-0x2
>
> Which is nice enough, but immediately after
At boot we dump the NUMA memory topology in dump_numa_memory_topology(),
at KERN_DEBUG level, resulting in output like:
Node 0 Memory: 0x0-0x1
Node 1 Memory: 0x1-0x2
Which is nice enough, but immediately after that we iterate over each
node and call setup_node_data(),