vparresources2.5 (2012 03)

v
vparresources2(5) vparresources2(5)
(For OA Based Partition Management Systems)
• Please note that unlike nPartitions, vPartition ilm_size and size are specified in MB (megabytes).
The commands round ilm_size and size upward as required to the granule increment in effect for that
memory type. ilm_size and size may be specified in decimal or in hexadecimal. A hex specification
should be preceded by 0x, as in 0x8000000.
Table II. Allowed Forms for Each Task
Task Forms # times/command
-a (add) cpu::num Once
cpu::cpu_path Multiple
cpu:::[min][:[max]] Once
socket:socket_id:cpu:: num (SLP) Once/socket_id
core::num Once
core:core_path Multiple
core:::[ min][:[max]] Once/socket_id
socket:socket_id:core:: num (SLP) Once/socket_id
io:io_path Multiple
ioslot:ioslot_path Multiple
mem::ilm_size Once
socket:socket_id:mem:: size (SLM) Once/socket_id
-m (modify) cpu::num Once
cpu:::[min][:[max]] Once
socket:socket_id:cpu:: num (SLP) Once/socket_id
core::num Once
core:::[ min][:[max]] Once
socket:socket_id:core:: num (SLP) Once/socket_ia
mem::ilm_size Once
socket:socket_id:mem:: size (SLM) Once/socket_id
-d (delete) cpu::num Once
cpu:cpu_path Multiple
socket:socket_id:cpu:: num (SLP) Once/socket_id
core::num Once
core:core_path Multiple
socket:socket_id:core:: num (SLP) Once/socket_id
io:io_path Multiple
ioslot:ioslot_path Multiple
mem::ilm_size Once
socket:socket_id:mem:: size (SLM) Once/socket_id
The forms above are subject to the following semantic rules enforced by the commands. Note that cpu
related modifications may be effected on a vPar even in
UP state. For any other resource modifications
(such as ioslot or memory), the vpar must be in
DOWN state.
• CPU-cores
1)
-a cpu::num or -a core::num specifies that num CPU-cores be added to the target vPar.
2)
-a cpu:cpu_path or -a core:core_path specifies that the CPU-core at resource path be added
to the target vPar. The CPU-core must not be assigned to any other vPar.
3)
-a socket:socket_id :cpu::num or -a socket:socket_id :core::num specifies that num
CPU-cores on socket socket_id (SLPs) be added to the target vPar.
4) No matter how they are specified, the total number of CPU-cores assigned to a vPar must always
be within the range specified by the
cpu:::min:max or core:::min:max specification.
5) For vPars that are DOWN,
-m cpu::num or -m core::num specifies that the total non-socket
specific CPU-cores in the vPar be set to num. This operation may result in addition or deletion of
CPU-cores.
6) For vPars that are UP,
-m cpu::num or -m core::num specifies that the total number of
CPU-cores in the vPar be set to num. This operation may result in addition or deletion of CPU-
cores. If the operation results in deletion of cores, the system can delete any set of cores (system
assigned, user assigned or socket specific) from that vPar and the associated count will be
modified accordingly.
8 Hewlett-Packard Company − 8 − HP-UX 11i Version 3: March 2012