Technical data

Processor Sets (Psets) on nPartitions
Examples: Sample Uses of Psets
HP System Partitions Guide: Administration for nPartitions—rp7410
EMSP—[e-mail]
346
2 8 0 0 5 95
0 9 0 1 9 90
2 11 0 0 8 92
system 9 0 7 84
#
Use the mpsched -u... command to unbind the “potato” program
(process ID 10368) from processor ID 3, to allow the program’s threads to
migrate to other processors in the Pset to which it is bound.
Then use sar to list the local nPar’s current processor usage, including
all processor and Pset details.
Since the “potato” program was unbound from processor 3, its threads
were able to migrate to the other processors in the Pset to which it
“potato” is bound (Pset 2).
All processors in Pset 2 are being used fairly heavily, while processors in
Pset 0 are 100% idle. This is due to Pset processor resource isolation: by
default each program only uses processors in the Pset in which it is run.
(The Pset programming interface can override this default to launch
threads and processes in other Psets, given the right conditions.)
# mpsched -u -p 10368
Pid 10368: not bound using the default process launch policy
# sar -u -M -P 1
HP-UX feshd5a B.11.11 U 9000/800 10/23/01
00:24:26 pset cpu %usr %sys %wio %idle
00:24:27 0 0 0 0 0 100
2 1 101 0 0 0
0 2 1 0 0 100
2 3 101 0 0 0
2 4 100 1 0 0
2 5 96 0 0 5
2 6 101 0 0 0
2 7 101 0 0 0
2 8 18 2 0 81
0 9 0 1 0 100
2 11 88 0 0 13
system 64 0 0 36
#
HP Restricted / DRAFT
DRAFT NOV 2001