vparresources2.5 (2010 09)

v
vparresources2(5) vparresources2(5)
(For OA Based Partition Management Systems)
7) Defaults: When a vPar is created, the following defaults are in effect:
• num:
0
• min: 0
• max: equal to the total number of active CPU-cores in the underlying nPartition.
You can modify these defaults with command line options to the
vparcreate or vparmodify
command when the vPar is down.
• Memory
1)
-a mem::size specifies that at least size MB ILM must be available. If size is not an integral
multiple of the ILM granularity, it is first rounded up to the next granule boundary before testing
for availability. By definition, this memory is of type ILM.
2)
-a socket:socket_id:mem::size specifies that at least size MB of memory on socket socket_id
must be available. If size is not an integral multiple of the SLM granularity, it is first rounded up
to the next granule boundary before testing for availability. By definition, this memory is of type
SLM.
3)
-m mem::size specifies that the total memory in the target vPar be set to size MB. This opera-
tion may result in assignment or deletion of memory. The
-m option is internally mapped to
either a
-a or -d option. The difference in the current memory size and the specified memory
size is rounded up before the addition or deletion. This may sometimes result in the new memory
to be more than the specified value if -m is internally mapped to -a or less than the specified
value if
-m is internally mapped to -d. Here are a few examples to illustrate the above.
Example 1:
Suppose the current memory value of the target vPar is 1024MB and the specified new memory
value using
-m is 1000MB. Also assume that the ILM granule size is set to 256MB. Since the
new specified value is less than the current value, the operation will be determined to be a "dele-
tion".
Current value - Specified value == Value to be deleted.
1024 - 1000 == 24.
24MB is not granule aligned;
hence, round up 24MB to the next granule 256MB.
So the command deletes 256MB from the current value resulting in 768MB which is less than
what the user asked for.
Example 2:
Suppose the current memory value of the target vPar is 1024MB and the specified new memory
value using
-m is 1025MB. Also assume that the ILM granule size is set to 256MB. Since the
new specified value is greater than the current value, the operation will be determined to be an
"addition".
Specified value - Current value == Value to be added.
1025 - 1024 == 1.
1MB is not granule aligned;
hence round up 1MB to the next granule 256MB.
So the command adds 256MB to the current value resulting in 1280MB which is more than what
the user asked for.
4)
-m socket:socket_id:mem::size specifies that the SLM from socket socket_id in the target
vPar be set to size MB. This operation may result in assignment or deletion of SLM. The -m
option is internally mapped to either a -a or -d option. The difference in the current memory
size and the specified memory size is rounded up before the addition or deletion. This may some-
times result in the new memory to be more than the specified value if -m is internally mapped to
-a or less than the specified value if -m is internally mapped to -d. Refer to the examples above.
Command Examples
If more than one task is specified in a command, they are processed in the order (left-to-right) in which
they are encountered on the command line. Some tasks will affect the outcome of others. Here is an
example of correct usage, as well as counterexamples within the description.
8 Hewlett-Packard Company − 8 − HP-UX 11i Version 3: September 2010