-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Mark Post wrote: > > > Actually, the needed parameter is either "additional_cpus=#" or > "possible_cpus=#". The additional_cpus parameter will cause the > kernel to reserve "#" more slots for CPUs than were detected at > boot time. The "possible_cpus" parameter will cause the kernel to > create exactly "#" slots for CPUs, no matter how many were detected > at boot time, even if the number is smaller than the number of CPUs > that were detected. Specifying possible_cpus will cause any > additional_cpus parameter to be ignored. > > The maxcpus (note the s on the end) parameter tells the kernel to > only _start_ "#" number of CPUs, even if more were detected at boot > time. If there were more defined, you can bring the others online > later (see below). If fewer CPUs were detected, maxcpus has no > real effect. > > If an additional CPU gets DEFINEd (via CP), or configured online > (in an LPAR), you then need to bring it online to the Linux system > by echoing a "1" into /sys/devices/system/cpu/cpu?/online, where ? > equals the number of the CPU, (starting with 0). > > Whew! > > Um, yeah. That's what happens to memory as you get older. Sorry working at home and couldn't reference our zipl.conf(s) directly, but possible_cpus=n seems like what we have been using. Once set high enough its something you don't need to change very often.
Mark -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFHMg+2+CA7PBRBnXQRAhhPAKCQ3VEL+fGYWXUARAeCreeFJvSmvwCfXBSE nhrqGU0NWmNX1S/CTBN6iy4= =ltjU -----END PGP SIGNATURE----- ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
