Hardware Management Console (HMC) Case Configuration Study for LPAR Management 25
Figure 13 Toggle the Capped/Uncapped option
You have to consider the number of virtual processors to be able to use all the
CPUs from the shared processor pool.
In our example, after the CoD operation, we have 3.0 available processing units
in the shared processor pool and 1 dedicated processor allocated to node oli.
The partition nicole_vio uses 0.8 processing units and is capped.
Partition julia uses 0.2 units and 1 virtual processor, and can use 1 physical CPU.
Adding 1 virtual CPU allows this partition to use a maximum of 2.0 processing
units.
In Example 10, we produced heavy CPU load on partition julia while the other
partition using the shared processor pool is in an idle state. The
physc parameter
shows the actual number of physical processing units used by partition julia.
Example 10 Output of topas -L
Interval: 2 Logical Partition: julia Tue Mar 31 16:20:46 1970
Psize: 3 Shared SMT OFF Online Memory: 512.0
Ent: 0.20 Mode: UnCapped Online Logical CPUs: 2
Partition CPU Utilization Online Virtual CPUs: 2
%usr %sys %wait %idle physc %entc %lbusy app vcsw phint %hypv hcalls
100 0 0 0 2.0 999.70100.00 1.00 200 0 0.0 0
===============================================================================
LCPU minpf majpf intr csw icsw runq lpa scalls usr sys _wt idl pc lcsw
Cpu0 0 0 527 258 234 4 100 65 100 0 0 0 1.00 83
Cpu1 0 0 211 246 209 2 100 520 100 0 0 0 1.00 117