LSF Version 7.3 - Using Platform LSF HPC

◆ CPU_LIST= cpu_ID_list ;
cpu_ID_list is a list of CPU IDs separated by commas. The CPU ID is a positive
integer or a range of integers. If incorrect CPU IDs are specified, the job remains
pending until the specified CPUs are available.
You must specify at least as many CPU IDs as the number of CPUs the job requires
(
bsub -n). If you specify more CPU IDs than the job requests, LSF selects the best
CPUs from the list.
◆ CPUSET_OPTIONS= option_list ;
option_list is a list of cpuset attributes joined by a pipe (|). If incorrect cpuset
attributes are specified, the job is rejected. See “Cpuset attributes” on page 138 for
supported cpuset options.
◆ MAX_CPU_PER_NODE=max_num_cpus;
max_num_cpus is the maximum number of CPUs on any one node that will be used
by this job. Cannot be used with the NODE_EX option.
◆ MEM_LIST= mem_node_list ;
(Altix ProPack 4 and ProPack 5) mem_node_list is a list of memory node IDs
separated by commas. The memory node ID is a positive integer or a range of
integers. For example:
"CPUSET[MEM_LIST=0,1-2]"
Incorrect memory node IDs or unavailable memory nodes are ignored when LSF
allocates the cpuset.
◆ NODE_EX=Y | N;
Allocates whole nodes for the cpuset job. This option cannot be used with the
MAX_CPU_PER_NODE option.
When a job is submitted using
-extsched, LSF creates a cpuset with the specified
CPUs and cpuset attributes and attaches it to the processes of the job. The job is then
scheduled and dispatched.
Running jobs on specific CPUs
The CPUs available for your jobs may have specific features you need to take advantage
of (for example, some CPUs may have more memory, others have a faster processor).
You can partition your machines to use specific CPUs for your jobs, but the cpusets for
your jobs cannot cross hosts, and you must run multiple operating systems
You can create static cpusets with the particular CPUs your jobs need, but you cannot
control the specific CPUs in the cpuset that the job actually uses.
A better solution is to use the CPU_LIST external scheduler option to request specific
CPUs for your jobs. LSF can choose the best set of CPUs from the CPU list to create a
cpuset for the job. The best cpuset is the one with the smallest CPU radius that meets
the CPU requirements of the job. CPU radius is determined by the processor topology
of the system and is expressed in terms of the number of router hops between CPUs.