HP-UX Workload Manager User's Guide

Configuring WLM
Defining SLOs
Chapter 5 197
NOTE For information on the effect of these keywords in passive mode, see
“Passive mode versus actual WLM management” on page 238.
Specify the lower and upper bounds on CPU resources for an SLO using
the following syntax:
mincpu = lower_bound_request;
maxcpu = upper_bound_request;
where
lower_bound_request
Is an integer from 0 to upper_bound_request,
inclusive. lower_bound_request is the minimum
number of CPU shares the SLO’s controller can
request.
If an SLO does not also contain a cpushares statement
or a goal statement, the mincpu value is used as the
SLO’s shares request. If an SLO does not contain a
mincpu statement, 0 is used as the SLO’s shares
request—although a gmincpu value or hmincpu value
may keep the allocation from actually being 0 shares.
lower_bound_request is out of the total CPU
resources, which is 100 multiplied by the number of
cores (if you set the tunable absolute_cpu_units to 1
or it is implied by other elements in your
configuration)—or just 100 by default.
To have a minimum request of 2 cores on an 8-core
system with absolute_cpu_units enabled
(absolute_cpu_units = 1), you would specify:
mincpu = 200;
If you specify a lower_bound_request greater than
the total CPU resources, WLM treats it as equal to the
total CPU resources.