vparresources.5 (2010 09)

v
vparresources(5) vparresources(5)
When you use the vparstatus command when the monitor is not running, or if you specify a database
other than the one currently loaded into the monitor, it displays
Requested resources. Otherwise it
displays
Effective resources.
Resources described in this manpage are
Effective resources unless noted otherwise.
RESOURCES
Different resource types call for different resource management. Each resource type and its management
is described below.
CPUs
The min/max specification, bound CPUs: In addition to defining the limits of the number of CPUs
assigned to a vPar, in HP-UX Release 11i, Version 1, the min specification also defined the number of
bound CPUs, those capable of processing I/O interrupts. This number could not be changed while the
vPar was running.
In HP-UX Release 11i, Version 2 (and later releases), all CPUs are capable of processing I/O interrupts,
and they may be added or deleted while the vPar is running, except for the boot processor, described
later. Therefore, the concept of "bound CPU" no longer has meaning. min and max now define only the
upper and lower limits of CPU assignment. The relation min
<= total CPUs <= max is always strictly
enforced. Although you can modify each value, you will get an error if this relationship is ever violated,
even in mid-command. This means
• You cannot delete CPUs such that total CPUs
< min,
• You cannot add them such that total CPUs > max,
• You cannot modify min if that would exceed total CPUs ,
• You cannot modify max to a value less than total CPUs.
If you do not specify min or max when creating a vPar, the following defaults apply:
• min =1.
• max = number of Enabled CPUs in the nPartition.
Although CPUs can be added to and deleted from a running vPar, the values for min or max can only be
changed if the vPar is
Down.
For the rest of this section, we assume that any CPU operation does not violate a min or a max require-
ment.
CPUs can be added (assigned) to a vPar in one of three ways. The result of the assignment can depend on
whether the vPar is running (
Up) or not running (Down).
• Non-cell-specific, or generic, assignment,
-a cpu::num. The monitor is free to assign any available
CPUs authorized by the iCAP product to satisfy num. See the section CPUs and Instant Capacity
(iCAP) later in this manpage for more information on iCAP. If the vPar is
Up, the CPUs are assigned
immediately, and, after a short initialization period, are available for use. During initialization, a
vparstatus command will show them as Pending.
If the vPar is
Down, num CPUs are allocated to the vPar if available and authorized, but the monitor
assigns specific CPUs only when the vPar is booted.
• Specific assignment by hardware path,
-a cpu:path. If this operation succeeds, the specified CPU is
assigned to the vPar. The CPU is permanently associated with the vPar unless it is deleted by
hardware path. The vparstatus -v command shows such CPUs as "User assigned".
The CPU must be available, that is, it must exist and not be assigned to another vPar. Also all CPUs
from the cell must not have already been reserved to either this or another vPar. If the operation
increases the total number of assigned CPUs, it must also be authorized by iCAP.
If the vPar is
Down, a specific assignment does not change the total number of CPUs assigned to the
vPar, hence iCAP does not need to authorize the action. But it also means that a specifically assigned
CPU must replace a previously allocated generic CPU. If there is none, the assignment fails.
Example: You have configured a vPar with
-a cpu::2. The vPar is Down. Now you enter -a
cpu:0.10 -a cpu:0.11. This works because the monitor assigns CPUs only when the vPar is
booted, so it will then use the specific two you assigned by path. But your total allocation is still two
CPUs. At this point, if you enter -a cpu:0.12, the request will fail because you have not allocated
a third CPU.
2 Hewlett-Packard Company − 2 − HP-UX 11i Version 3: September 2010