boot_cpuset(4)							boot_cpuset(4)

NAME    [Toc]    [Back]

     boot_cpuset.conf, boot_cpuset.so -	boot cpuset configuration tool

SYNOPSIS    [Toc]    [Back]

     boot_cpuset.so is loaded and executed by init

DESCRIPTION    [Toc]    [Back]

     The boot_cpuset.so	library	provides a method for putting init(1M) into a
     cpuset(4).	 Since all "standard" processes	are descendents	of init, this
     means that	all standard processes on the system (daemons, interactive,
     etc.)  will be confined to	that cpuset.  The cpuset is named boot.

     The boot_cpuset.so	library	is normally installed on SGI ccNUMA systems.
     If	it is found in /lib32 by init, it will be loaded and executed.	The
     behaviour of the library is controlled by /etc/config/boot_cpuset and
     /etc/config/boot_cpuset.config. The former	file follows the chkconfig(1M)
     convention	and may	be manipulated by chkconfig. If	it contains the	word
     on, creation of the cpuset	will proceed unless an error occurs. If	off is
     found, the	library	will exit and normal init processing will resume.  The
     /etc/config/boot_cpuset.config file follows the syntax convention of
     cpuset(4).	All restrictions specified in miser_cpuset(1) apply.

FILES    [Toc]    [Back]

     /etc/config/boot_cpuset	       Follows chkconfig(1M) convention. If
				       off, no further processing occurs and
				       init will resume.

     /etc/config/boot_cpuset.config    Configuration file specifing the
				       cpuset. See cpuset(4) for more
				       information.

WARNINGS    [Toc]    [Back]

     No	attempt	is made	to check the configuration file	for a reasonable
     configuration. Specifying an unreasonable configuration may leave system
     non-functional.

     Note: The cpuset is not activated if the system is	booted into single
     user mode.	This provides an escape	mechanism should the configuration
     prove to be unreasonable.

     Processes that are	moved out of a cpuset (any) will be left outside of
     all cpusets and not returned to the boot cpuset. To work around this
     problem, the process should reattach itself to the	boot cpuset rather
     than be moved it out of the source	cpuset.

NOTES    [Toc]    [Back]

     Allthough this mechanism can be used in a standalone fashion with the
     cpuset(1) command,	it is primarily	intended for use by batch systems. Due
     to	the above noted	limitation of moving processes between cpusets,	it may
     not practical to dynamically re-adjust resources for running processes or
     jobs.



									Page 1






boot_cpuset(4)							boot_cpuset(4)

SEE ALSO    [Toc]    [Back]

     init(1M), miser_cpuset(1),	cpuset(4).


									PPPPaaaaggggeeee 2222