Technical data

Processor Sets (Psets) on nPartitions
Examples: Sample Uses of Psets
HP System Partitions Guide: Administration for nPartitions—rp7410
EMSP—[e-mail]
345
Use the mpsched command to run the “potato” program and bind it to
processor ID 2. Then use the psrset -q... command to list the Pset
binding for “potato” (process ID 10368); “potato” is bound to Pset 0.
# mpsched -c 2 ./potato -n 7
Pid 10368: bound to processor 2 using the default process launch policy
Threads = 7
tid = 2 cpu = 2
tid = 3 cpu = 2
tid = 4 cpu = 2
tid = 5 cpu = 2
tid = 6 cpu = 2
tid = 7 cpu = 2
tid = 1 cpu = 2
# psrset -q 10368
PID 10368 PSET 0
#
Use the psrset -b... command to change the Pset binding for “potato”
to Pset 2. Then use psrset -q... to confirm that it is bound to Pset 2,
and use the mpsched -q... command to check its processor binding.
# psrset -b 2 10368
successfully bound pid 10368 to pset 2
# psrset -q 10368
PID 10368 PSET 2
# mpsched -q -p 10368
Pid 10368: bound to processor 3 using the default process launch policy
#
Use the sar command to list the current nPar’s processor usage,
including Pset details. Note that processor ID 3 in (Pset 2) is heavily
loaded by the “potato” program.
# sar -u -M -P 1
HP-UX feshd5a B.11.11 U 9000/800 10/23/01
00:17:11 pset cpu %usr %sys %wio %idle
00:17:12 0 0 0 0 7 92
2 1 0 0 10 90
0 2 0 0 8 92
2 3 100 0 0 0
2 4 0 0 4 96
2 5 0 0 8 92
2 6 0 0 7 93
2 7 0 0 9 91
HP Restricted / DRAFT
DRAFT NOV 2001