number of processors on vpars

[David Markus]

We have a system whichs is divided in 2 vPars. The total number of CPU's for the system is 8, vPar1 has 6 and vPar2 has 2.

When I check the number of processors with:
# echo runningprocs/D | adb -k /stand/vmunix /dev/kmem

it says it has 5 runningprocs, while only 2 cpu's are active, as shown with vparsstatus.

- Am I right to assume the '5' represents the number of kernel entries it has for the bound/unbound CPU's it has and used to have?

[Chan 007]

dav,

check with top or ioscan what is the o/p you get?

Do you have PRM configured in your system?

Chan

[Pete Randall · Accepted solution]

David,

What do you get when you run

ioscan -k |grep -n processor |wc -l

?


Pete

[David Markus]

here's some info :

# ioscan -k |grep -n processor |wc -l
5

#vparstatus
Name Min/Max Bound/Unbound
vpar1 3/6 3 3
vpar2 2/3 2 0

#cstm output :
72 14/13 CPU (880) Information Successful
73 14/14 CPU (880) Information Successful
74 14/15 CPU (880) Information Incomplete
75 14/16 CPU (880) Information Incomplete
76 14/17 CPU (880) Information Incomplete

cstm gives me no futher information about cpu 15/16/17 except its hardware path...

[Chauhan Amit]

a) were all CPU visible earlier ?? when did u notice this thing
b) are you using icod ?? If yes then what is the output of #icod_stat
c) what does ioscan output suggests on other vpar ?

-Amit

[David Markus]

Sorry for this late responce, I was away this week.

@Amit:
a: Not sure, never noticed it before.
b: icod has got nothing to do with it (i think), because it just shows the total amount of procs for the nPar (which is 8) and does not give any vPar info.
c: I'll have to get back on this when I return to office next week.

[David Markus]

We've shuffled around with some processors and I came to the conclusion that the output of

#echo runningprocs/D | adb -k /stand/vmunix /dev/kmem
7

indeed represents the number of kernel entries for bound/unbound CPUs.

The nPar has 8 CPU's devided over 2 vPars; vPar1 has 1 bound and 6 unbound CPUs and vPar2 has 1 bound CPU. Because unbound CPUs can be moved dynamically between vPars vPar2 also holds kernel entries for the unbound CPUs of vPar1. This means it has 7 entries. Which equals the output of my previous command.

So the defenition of 'runningpocs' isn't the total amount of processors IN use, but the total amount of processors it CAN use.