HP Superdome 2 Partitioning Administrator Guide (5900-2064, November 2011)

or, for this example, run the following command.
# # ioscan -m resourcepath | grep 48/0/0/2/0
48/0/0/2/0 0x900010002ffff8e iorp-9/1/0/0/2
48/0/0/2/0/0 0x90001000203ff85 ioslot-9/1/3
Memory
There are two major types of memory addressing, Socket Local Memory (SLM), and InterLeaved
Memory (ILM). With SLM, entire memory address ranges are from a single socket. For best
performance, memory and CPU-cores from the same sockets must be assigned to a vPar. ILM is
an address range of memory whose adjacent addresses reside on one or more sockets in the
underlying nPartition.
Memory Granularity
The nPartition memory is divided into multiple memory granules by firmware to assign memory
easily to vPars. The size of these memory granules can be optionally specified by the user. Memory
granularity refers to the size of these memory granules.
NOTE: The memory granules are not the actual memory DIMMs.
You can specify the granularity for SLM and ILM separately. However, the following applies to
both types of memory:
• Memory granularity is specified during the creation of nPartition. Any modification thereafter
requires you to reboot the nPartition.
• The minimum values (ILM and SLM granularity) are 256 MB.
• The default value is OS dependent and may be adjusted based on the total memory available
in the nPartition.
• Memory is assigned to virtual partitions in multiples of granule sizes.
HP recommends to retain the default memory granularity value chosen by the system, unless there
is a specific requirement to change it.
Assigning Memory to a vPar
• The -a mem::size option is used to assign size megabytes of ILM to a vPar.
• The -a socket:socket_id:mem::size option assigns size megabytes of SLM from socket
socket_id to a vPar.
If size is not an integral multiple of the granularity of the specified memory type, vPars normally
adjusts it upward to the next granule boundary.
In a vPar environment, either of the above command-line options allows the system to reserve the
available indicated memory. Thus, it is possible to define vPars with more memory than nPartition.
Actual memory ranges are only assigned to the vPar when it is booted. The memory ranges might
vary for every boot sequence.
I/O
The vPar assignable IO resources are rootports or ioslots in the blades and I/O bays. Each I/O
bay consists of an iohub, which is the chip that supports up to three root complexes. The rootports
live under a root complex. Each root complex supports two rootports, providing a total of up to
six PCIe slots per iobay. The iohub and root complex are elements in the I/O hierarchy leading
upto the rootport in a BIOX. However, vPar assignable resources occur at the rootport level, with
the iohub and root complex included in the resourcepath leading upto it. Rootports and ioslots are
the ways of representing I/O resources. The
nl
parstatus -c enclosure#/blade# -V command provides the rootport to ioslot mapping
for the I/O resources on a blade. Similarly, the parstatus -i IOX#/IObay# -V command
Planning Your Virtual Partitions 87