From: Holger.VanKoll@SWISSCOM.COM
Date: Fri Feb 14 2003 - 11:04:32 EST
cpu_deallocate logical_cpu_number
those are the numbers bindprocessor -q gives out, normally sequentially
numbered
to check disabling:
lsattr -El procxx
xx is *not* this logical number, but what you see in the "xx+1-th" line
of lsdev -Cc processor output
on my 16-cpu p670 I have 0-15 as logical numbers and proc
0,1,2,3,4,5,6,7,16,17,..,23 ; dunno why
-----Original Message-----
From: justin.bleistein@SUNGARD.COM [mailto:justin.bleistein@SUNGARD.COM]
Sent: Friday, February 14, 2003 4:40 PM
To: aix-l@Princeton.EDU
Subject: Re: enabling cpu guard
What's the syntax of cpu_deallocate then once the command runs how would
you know it's disabled?
--Justin Richard Bleistein
Unix Systems Administrator (Sungard eSourcing)
Desk: (856) 866 - 4017
Cell: (856) 912 - 0861
Email: justin.bleistein@sungard.com
Holger.VanKoll@SW
ISSCOM.COM To:
aix-l@Princeton.EDU
Sent by: IBM AIX cc:
Discussion List Subject: enabling cpu
guard
<aix-l@Princeton.
EDU>
02/14/2003 09:28
AM
Please respond to
IBM AIX
Discussion List
Hello,
I tried to turn off processors with cpu_deallocate. It does not work and
I found out I probably have to enable cpu guard ( chdev -l sys0
cpuguard=enable ).
Its disabled by default. I fail to see why.
What is the disadvantage; why should one not want to use this feature?
Regards,
Holger
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 22:16:35 EDT