vparresources.5 (2010 09)

vparresources(5) vparresources(5)

If the vPar is

Up, the result varies as follows:

• If path is that of a generically-allocated CPU that the monitor assigned to the vPar when it was

booted, it changes to be speciﬁcally assigned. It will remain associated with the vPar until deleted

by speciﬁc path. But the total CPU count does not change, hence iCAP need not authorize the

operation.

• If the speciﬁed CPU is not assigned to a vPar, it is added to your vPar and remains associated with

it until deleted. The total CPU count increases by 1, so iCAP must authorize the addition.

Hewlett-Packard recommends that users conﬁgure speciﬁc CPUs only when required for performance,

and that you do not mix user-assigned CPUs and cell-local processors (next bullet) in the same data-

base. Where performance is not a consideration, specify only generic assignments and allow the moni-

tor to manage assignment of CPUs.

• Assignment by specifying a cell,

-a cell:

cell_id :cpu::num. The monitor is free to assign any

num available CPUs from cell cell_id . CPUs assigned in this way are referred to as cell-local proces-

sors or CLP.

As with generic assignment, if the vPar is

Up, the CPUs are assigned immediately. If it is Down, they

are allocated, but speciﬁc CPUs are only assigned when the vPar is booted. In either case, the CPUs

must be available and their addition authorized by iCAP.

Hewlett-Packard recommends that users conﬁgure CLPs only when required for performance, and

that you do not mix CLPs and user-assigned processors (previous bullet) in the same database. Where

performance is not a consideration, specify only generic assignments and allow the monitor to manage

assignment of CPUs.

Any CPU assigned to a running vPar can be deleted by specifying its hardware path. Except for that con-

dition, if a CPU is to be deleted later, it must be deleted the same way it was assigned. For example, if

you have conﬁgured a (

Down) vPar as follows:

-a cpu::4

-a cpu:0.12

-a cell:3:cpu::2

you will have six CPUs in your conﬁguration. (Recall that the total CPU count does not change when

adding a user assigned CPU to a Down vPar.) In this case, you have replaced one generically speciﬁed

CPU with a user assigned CPU, leaving three generically assigned.

With this conﬁguration, you are only allowed to delete three CPUs generically, using

-d cpu::3

You will get a command error if you specify a higher number. Similarly, the two CLP CPUs can only be

deleted via a CLP deletion.

No matter how you choose to add and delete CPUs, the total must always remain between the min and

max speciﬁcation for the vPar.

To help you manage these limitations, the

vparstatus command displays the count of CPUs in the

various categories when the -v (detailed display) or the -M (machine-readable) options are used. Here is

the CPU portion of the detailed display for the above conﬁguration:

HP-UX 11i Version 3: September 2010 − 3 − Hewlett-Packard Company 3