LSF Version 7.3 - Using Platform LSF HPC

◆ The new cpuset integration cannot coexist with the old integration within the same
cluster
◆ Under the MultiCluster lease model, both clusters must use the same version of the
cpuset integration
Since backfill and slot reservation are based on an entire host, they may not work
correctly if your cluster contains hosts that use both static and dynamic cpusets or
multiple static cpusets.
Jobs submitted to a chunk job queue are not chunked together, but run as individual LSF
jobs inside a dynamic cpuset.
◆ When LSF selects cpuset jobs to preempt, specialized preemption preferences, such
as MINI_JOB and LEAST_RUN_TIME in the PREEMPT_FOR parameter in
lsb.params, and others are ignored when slot preemption is required.
◆ Preemptable queue preference is not supported.
Job pre-execution programs run within the job cpuset, since they are part of the job. By
default, post-execution programs run outside of the job cpuset.
If JOB_INCLUDE_POSTPROC=Y is specified in
lsb.applications, post-
execution processing is not attached to the job cpuset, and Platform LSF does not
release the cpuset until post-execution processing has finished.
Jobs suspended (for example, with bstop) will release their cpusets.
◆ SGI Altix Linux ProPack versions 4 and lower do not support memory
migration; you must define RESUME_OPTION=ORIG_CPUS to force LSF to
recreate the original cpuset when LSF resumes a job.
◆ SGI Altix Linux ProPack 5 supports memory migration and does not require
additional configuration to enable this feature. If you submit and then suspend a job
using a dynamic cpuset, LSF will create a new dynamic cpuset when the job resumes.
The memory pages for the job are migrated to the new cpuset as required.
◆ SGI Altix Linux ProPack 3 only supports
CPUSET_OPTIONS=CPUSET_MEMORY_LOCAL. If the cpuset job runs on
an Altix host, other cpuset attributes are ignored.
◆ SGI Altix Linux ProPack 4 and ProPack 5 do not support
CPUSET_OPTIONS=CPUSET_MEMORY_MANDATORY or
CPUSET_OPTIONS=CPUSET_CPU_EXCLUSIVE attributes. If the cpuset job
runs on an Altix host, the cpusets created on the Altix system will have their
memory usage restricted to the memory nodes containing the CPUs assigned to the
cpuset. The CPUSET_MEMORY_MANDATORY and
CPUSET_CPU_EXCLUSIVE attributes are ignored.
◆ SGI Altix Linux ProPack 4 and ProPack 5 static cpuset definitions must include
both the cpus and the memory nodes on which the cpus reside. The memory node
assignments should be non-exclusive, which allows other cpusets to use the same
nodes. With non-exclusive assignment of memory nodes, the allocation of cpus will
succeed even if the cpuset definition does not correctly map cpus to memory nodes.
PAM on IRIX cannot launch parallel processes within cpusets.