This was failing on Crusher login nodes at least (which are 4-way NUMA).
When I instrumented it to figure out what it actually does I noticed that at least on that system it was skipping the highest-number NUMA node so I fixed that as well.
Tested on a 4-node NUMA and a 1-node (non-NUMA) system.
This was failing on Crusher login nodes at least (which are 4-way NUMA).
When I instrumented it to figure out what it actually does I noticed that at least on that system it was skipping the highest-number NUMA node so I fixed that as well.
Tested on a 4-node NUMA and a 1-node (non-NUMA) system.