vparresources.5 (2010 09)

v
vparresources(5) vparresources(5)
Table I. Resource syntax summary
Resource Form # times/command
CPU cpu:path Multiple
cpu::num Once
cpu:::[min][:[max]] Once
cell:cell_id:cpu::num (CLP) Once per cell_id
I/O io:h/w path[:attr1[,attr2]] Multiple
Memory mem::size[:base|floating] (ILM) Multiple
mem:::base:range[:base|floating]Multiple
cell:cell_id:mem::size[:base|floating] Twice per cell_id
(CLM)
The first field is always one of the (case-insensitive) strings
cpu, io, mem,orcell.
num, min, and max are all positive integers. cell_id must be greater than or equal to 0.
size and range are positive 64-bit integers in units of megabytes. base is an unsigned 64-bit integer in
units of bytes. The commands round each of them upward as required to the granule increment in effect
for that memory type. size, range, and base may each be specified in decimal or in hexadecimal. A hex
specification should be preceded by
0x,asin0x8000000.
The last optional field for the memory specification can be either
base or floating
. If this field is not
specified, the default is type base.
The attributes for the I/O specification are zero, one, or many of the following (case-insensitive) strings:
ALTBOOT, TAPE, and BOOT. If more than one are specified, then they must be separated by a comma.
Each of the attributes can be assigned to no more than one I/O device. If it is already assigned to a dev-
ice, a new assignment silently de-assigns it from its present device. However, one device can associate
both attributes. This means it is possible for one device to own all ALTBOOT, TAPE and BOOT attri-
butes, but it is not possible for two or more devices to own BOOT.
Users must guard against assigning an attribute to an inappropriate device, for example, assigning
BOOT to a tty. The commands do not check for this, nor do they prevent it.
12 Hewlett-Packard Company − 12 − HP-UX 11i Version 3: September 2010