LSF Version 7.3 - Using Platform LSF HPC

Using LSF with SGI Cpusets
Specifying cpuset properties for jobs
To specify cpuset properties for LSF jobs, use:
◆ The -extsched option of bsub.
◆ DEFAULT_EXTSCHED or MANDATORY_EXTSCHED, or both, in the queue
definition (
lsb.queues).
If a job is submitted with the
-extsched option, LSF submits jobs with hold, then
resumes the job before dispatching it to give time for LSF to attach the
-extsched
options. The job starts on the first execution host.
For more information about job operations, see Administering Platform LSF.
For more information about
bsub, see the Platform LSF Command Reference.
-ext[sched] "[SGI_]CPUSET[ cpuset_options ]"
Specifies a list of CPUs and cpuset attributes used by LSF to allocate a cpuset for the job.
where cpuset_options are:
◆ CPUSET_TYPE=static |dynamic | none;
Specifies the type of cpuset to be allocated.
If you specify
none, no cpuset is allocated and you cannot specify any other cpuset
options, and the job runs outside of any cpuset.
◆ CPUSET_NAME= name ;
name is the name of a static cpuset. If you specify CPUSET_TYPE=static, you must
provide a cpuset name. If you specify a cpuset name, but specify CPUSET_TYPE
that is not static, the job is rejected.
◆ MAX_RADIUS= radius ;
radius is the maximum cpuset radius the job can accept. If the radius requirement
cannot be satisfied the job remains pending.
MAX_RADIUS implies that the job
cannot span multiple hosts. Platform LSF puts each cpuset host into its own group
to enforce this when MAX_RADIUS is specified.
◆ RESUME_OPTION=ORIG_CPUS;
Specifies how LSF should recreate a cpuset when a job is resumed.
By default, LSF tries to create the original cpuset when a job resumes. If this fails,
LSF tries to create a new cpuset based on the default memory option.
❖ ORIG_CPUS specifies that the job must be run on the original cpuset when it
resumes. If this fails, the job remains suspended.