Locality-Optimized Resource Alignment for Superdome 2

14
as evenly as possible, while still respecting the memory granule size: 20 GB from one socket and 21
GB from two others.
The second virtual partition in the table, dog, requires 70 GB of memory, so it also will not fit within
one or even two localities. Once again, the strategy is to confine it within the minimum number of
localities, which is three, and divide the resources as evenly as possible among the three localities. In
this case, three sockets each contribute 2 cores and around 21 GB of local memory, with 9 GB of
memory coming from ILM.
Here are commands that could be used to establish the configuration for the first two virtual partitions:
vparcreate -N 2 -p cow -a mem::9GB
vparmodify -p 2:cow -a socket:1/1/0:cpu::3 -a socket:1/1/0:mem::20GB
vparmodify -p 2:cow -a socket:1/1/1:cpu::3 -a socket:1/1/1:mem::21GB
vparmodify -p 2:cow -a socket:1/3/0:cpu::3 -a socket:1/3/0:mem::21GB
vparcreate -N 2 -p dog -a mem::9GB
vparmodify -p 2:dog -a socket:1/3/1:cpu::2 -a socket:1/3/1:mem::20GB
vparmodify -p 2:dog -a socket:1/5/0:cpu::2 -a socket:1/5/0:mem::21GB
vparmodify -p 2:dog -a socket:1/5/1:cpu::2 -a socket:1/5/1:mem::21GB
The first two virtual partition assignments are shown in the following diagram:
Figure 5. The first two virtual partitions configured according to LORA rules
To complete the configuration, the virtual partitions elk and fox must be constructed out of the
remaining resources. Each instance needs 21 GB of local memory and 3 GB of interleaved memory,