diff options
author | Nikunj A Dadhania <nikunj@linux.vnet.ibm.com> | 2015-07-02 11:09:01 +0530 |
---|---|---|
committer | Michael Ellerman <mpe@ellerman.id.au> | 2015-08-18 19:34:41 +1000 |
commit | 1d805440a364b4a68562e70119d8f94456698e55 (patch) | |
tree | de592ddd17f3d4849aeb6576f9052f101a54d130 /arch/powerpc/mm/slice.c | |
parent | 53522982fc3c254bb4444c336cb005c8636930c8 (diff) | |
download | talos-op-linux-1d805440a364b4a68562e70119d8f94456698e55.tar.gz talos-op-linux-1d805440a364b4a68562e70119d8f94456698e55.zip |
powerpc/numa: initialize distance lookup table from drconf path
In some situations, a NUMA guest that supports
ibm,dynamic-memory-reconfiguration node will end up having flat NUMA
distances between nodes. This is because of two problems in the
current code.
1) Different representations of associativity lists.
There is an assumption about the associativity list in
initialize_distance_lookup_table(). Associativity list has two forms:
a) [cpu,memory]@x/ibm,associativity has following
format:
<N> <N integers>
b) ibm,dynamic-reconfiguration-memory/ibm,associativity-lookup-arrays
<M> <N> <M associativity lists each having N integers>
M = the number of associativity lists
N = the number of entries per associativity list
Fix initialize_distance_lookup_table() so that it does not assume
"case a". And update the caller to skip the length field before
sending the associativity list.
2) Distance table not getting updated from drconf path.
Node distance table will not get initialized in certain cases as
ibm,dynamic-reconfiguration-memory path does not initialize the
lookup table.
Call initialize_distance_lookup_table() from drconf path with
appropriate associativity list.
Reported-by: Bharata B Rao <bharata@linux.vnet.ibm.com>
Signed-off-by: Nikunj A Dadhania <nikunj@linux.vnet.ibm.com>
Acked-by: Anton Blanchard <anton@samba.org>
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Diffstat (limited to 'arch/powerpc/mm/slice.c')
0 files changed, 0 insertions, 0 deletions