IBM Power 595, Технический обзор и введение

Страница: 148 / 188

136
IBM Power 595 Technical Overview and Introduction
IBMs logical partitioning strategy allows any processor core to be shared with any partition on
the system, thus enabling the following sequential scenarios for processor deallocation and
sparing:
1. When available, an unlicensed Capacity on Demand (CoD) processor core is by default
automatically used for dynamic processor sparing.
2. If no CoD processor core is available, the POWER Hypervisor attempts to locate an
unallocated core somewhere in the system.
3. If no spare processor core is available, the POWER Hypervisor attempts to locate a total
of 1.00 spare processing units from a shared processor pool and redistributes the
workload.
4. If the requisite spare capacity is not available, the POWER Hypervisor determines how
many processing units each partition is required to relinquish to create at least 1.00
processing unit shared processor pool.
5. When a full core equivalent is attained, the CPU deallocation event occurs.
Figure 4-3 shows CoD processor cores that are available for dynamic processor sparing.
Figure 4-3 Dynamic processor deallocation and dynamic processor sparing
The deallocation event is not successful if the POWER Hypervisor and operating system
cannot create a full core equivalent. This results in an error message and the requirement for
a system administrator to take corrective action. In all cases, a log entry is made for each
partition that could use the physical core in question.
POWER Hypervisor
Physical shared-processor pool
Dedicated processor
partitions
Set of micro-partitions
Dedicated processors
Shared-Processor Pool 0
pv
KEY:
pv physical processor
vp virtual processor
lp logical processor
PrU Processing Units
lp lp lp lp lp lp
A
IX V5.3
0.7
5
P
rU
lp lp lp lp lp lp lp lp
A
IX V6.
1
1.
5
PrU
Linux
0.7
5
P
rU
A
IX V5.3
A
IX V6.
1
pv pv pv pv pv
Avail
pv
vp vp
1
De
al
loc
a
te
vp vp
5
Avail
pv