vparresources2.5 (2012 03)

v
vparresources2(5) vparresources2(5)
(For OA Based Partition Management Systems)
Where performance is not a consideration, specify only generic assignments and allow the system to
manage assignment of CPU-cores.
For DOWN vPars, any CPU-core assigned to a vPar can be deleted the same way it was assigned or by
specifying the resource path. For example, if you have configured a vPar as follows:
-a cpu::4
-a cpu:3/1/0/2
-a socket:3/2/0:cpu::2
you will have seven CPU-cores in your vPar configuration. With this configuration, you are allowed only
to delete four CPU-cores generically, using
-d cpu::4
You will get a command error if you specify a higher number.
Similarly, the two SLP CPU-cores can only be deleted via a SLP deletion
-d socket:3/2/0:cpu::2
To delete the CPU-core specified by resource path, you need to delete it by specifying the resource path
-d cpu:3/1/0/2
For vPars that are UP, any CPU-core assigned to a vPar can be deleted in the same way it was assigned
or as part of deletion by count or as part of deletion by specifying socket id and count if the CPU-core
belongs to the specified socket. CPU-core deletion by count does not respect the path and socket bindings.
This means that when a CPU-core is deleted by count, it can delete the one which is added by path or by
socket locality. However the associated locality counts will get modified accordingly.
The example below illustrates the deletion behavior, if you have configured a vPar as follows:
-a cpu::4
-a cpu:3/1/0/2
-a socket:3/1/0:cpu::2
You will have seven CPU-cores in your vPar configuration. With this configuration, you are allowed to
delete a maximum of six CPU-cores generically, using
-d cpu::6
You will get a command error if you specify a higher number. This command can delete user assigned
and socket specific cores as well. There is no priority given to which type (user specified, system
assigned, socket specific) of CPU-cores are chosen first for deletion. For example, with the above vPar
configuration,
-d cpu::4
can delete one core which is assigned by path and 2 cores which are assigned as socket specific and one
core which is added by count, leaving 3 generic cores assigned to the partition.
Similarly, all the cores belonging to a socket irrespective of how they are assigned (user assigned, socket-
specific or system specified) can be deleted by specifying the socket id and a count, where count must not
exceed the total number of cores assigned from socket id and the vPar is left with at least one core after
the deletion. For example, with the above vPar configuration,
-d socket:3/1/0:cpu::3
will delete one CPU-core (3/1/0/2) which is user assigned and two CPU-cores which were assigned as
socket specific from the vPar.
Any of the seven cores can be deleted by specifying the resource path; for example
-d cpu:3/1/0/1
deletes the CPU-core 3/1/0/1 which is added as a socket specific core.
No matter how you choose to add and delete CPU-cores, the total must always remain between the min
and max specification for the vPar.
To reflect the actual configuration of cores in the virtual partition, the
vparstatus command displays
the count of CPU-cores in the various categories when the -v (detailed display) option is used. Here is
the CPU-core portion of the detailed display for the above configuration:
HP-UX 11i Version 3: March 2012 − 3 − Hewlett-Packard Company 3