The 'numa_node' reported by ndctl list -N should match the physical NUMA node
# ndctl list -N -v
[
{
"dev":"namespace1.0",
"mode":"fsdax",
"map":"dev",
"size":1065418227712,
"uuid":"8420bbe0-31de-4df8-87f0-94148d7121ee",
"raw_uuid":"70431086-7b4c-4e01-9a0d-80baad90ecd7",
"sector_size":512,
"align":2097152,
"blockdev":"pmem1",
"numa_node":0, <<<<< Should be 1
"target_node":3
},
{
"dev":"namespace0.0",
"mode":"fsdax",
"map":"dev",
"size":1065418227712,
"uuid":"dcfe052c-258e-40f9-9e79-625dccb4b2a6",
"raw_uuid":"9dbdd382-3bcd-43b9-8a17-3c51743cc6c0",
"sector_size":512,
"align":2097152,
"blockdev":"pmem0",
"numa_node":0, <<< Good
"target_node":2
}
]
A simple test is to check the numa_node value matches the dev value. eg: (numa_node = 1) == (namespace1.0), where namespaceX.Y -> X = NUMA Node, Y = Instance.
This could also be cross-referenced with the 'numa_node' values in /sys
# cat /sys/bus/nd/devices/namespace*/numa_node
0
0
0 <<< Should be 1
0 <<< Should be 1
The 'numa_node' reported by
ndctl list -N
should match the physical NUMA nodeA simple test is to check the
numa_node
value matches thedev
value. eg: (numa_node = 1) == (namespace1.0), where namespaceX.Y -> X = NUMA Node, Y = Instance.This could also be cross-referenced with the 'numa_node' values in /sys
Two physical NUMA nodes exist
Need to be aware of Sub-NUMA Clustering