LSF Version 7.3 - Using Platform LSF HPC

LSF host preference and RMS allocation options
Host preference partition (for example, bsub -m hostA) is only supported for
RMS_SLOAD allocation. LSF host preference is not taken into account for
RMS_SNODE and RMS_MCONT allocation. All hosts in the preference list must be
within the same host group or RMS partition.
LSF sorts nodes according to RMS topology (numbering of nodes and domains), which
takes precedence over LSF sorting order. LSF host preferences (for example,
bsub -m hostA) are not taken into account.
LSF sorts nodes based on host preference and load information, which take precedence
over RMS topology (numbering of nodes and domains).
The allocation starts from the first host specified in the list of LSF hosts and continues
until the allocation specification is satisfied.
LSF sorts nodes based on RMS topological order (numbering of nodes and domains);
LSF host preferences are not taken into account.
RMS rail allocation options
Rails are the layers of a Quadrics switch network. In multirail systems, you can specify
the following rail allocation options:
◆ rails=number
Specifies the number of rails required, where 1 <= number <= 32
OR
◆ railmask= bitmask
Specifies which rails are required, using bitmask to select them
Specify either
rails or railmask, but not both.
To use the RMS rail options with LSF jobs, use the -extsched option of bsub:
[rails= number | railmask= bitmask ]
For example, The following job uses 2 rails.
bsub -n 4 -q rms -extsched "RMS[RMS_MCONT; rails=2]"
-I Allocate immediately or fail LSF overrides; uses immediately to allocate
-N Number of nodes to use -extsched "RMS[nodes=nodes]"
-n Number of CPUs to use -n
-R immediate same as -I LSF overrides
rails Passed with -extsched
railmask Passed with -extsched
-i/ -o/ -e Input/output/error redirection bsub -i/ -o/ -e
-m Block or cyclic job distribution Must be passed directly (not via LSF) by the user on prun command
line.