System information

392 Logical Partitions on System i5
򐂰 Shared Processor Pool Units: Specifies the total number of processing units that will be
available to the partition after the resources are removed. In this example, the i5/OS
partition will be left with 100 processing units, or a full processor after we have removed
the CPU resources.
򐂰 Minimum / Maximum Shared Processor Pool Units: A minimum of 0.10 processing
units is required for every full processor that may be utilized for the given partition. In our
example, since we have a maximum of 2 processors that the i5/OS partition can utilize,
the minimum value is therefore required to be set to 0.20 processing units with a
maximum of 200 processing units, or 2 processors.
򐂰 Uncapped processing: By changing the value from 2= NO, to 1=YES, the partition may
utilize excess shared processor cycles. The quantity assigned is dependent on the setting
of the uncapped processing weight field that follows. If the value is 2=NO, then this
partition will not be assigned excess shared processor cycles and will be a capped
partition.
A capped partition indicates that the logical partition will never exceed its assigned
processing capacity. The capped mode could be used if you know that a software
application would never require more than a certain amount of processing power. Any
unused processing resources will be used only by the uncapped partitions in the shared
processor pool.
A partition using the uncapped mode indicates that the partition's assigned current
processing capacity can be exceeded, up to the partition's current virtual processor setting
when the shared processor pool has any unused processing power.
򐂰 Uncapped Processing Weight: With Virtual Partition Manager, since you can only
create 4 additional Linux partitions, this range is restricted to a set of predefined values:
0=None, 64=Low, 128=Medium and 255=High. By setting the uncapped weight (255
being the highest weight), any available unused capacity is distributed to contending
logical partitions in proportion to the established value of the uncapped weight. The default
uncapped weight value is 128. For example, if partition 2 had an uncapped weight of 64
and partition 3 had an uncapped weight of 255, partition 3 would get up to four times the
unused processing resources that partition 3 received. A value of zero will be required to
be set for partitions that are capped.
Note: Considering that Virtual Partition Manager does not support dynamic movement of
resources, you might want to define your partitions as uncapped partitions to automatically
assign unused processing units to a partition that needs the resources.