Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
S
Slurm
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
tud-zih-energy
Slurm
Commits
b85668f0
Commit
b85668f0
authored
17 years ago
by
Moe Jette
Browse files
Options
Downloads
Patches
Plain Diff
try to better spell out mpi use
parent
b659e63c
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/man/man1/srun.1
+22
-24
22 additions, 24 deletions
doc/man/man1/srun.1
with
22 additions
and
24 deletions
doc/man/man1/srun.1
+
22
−
24
View file @
b85668f0
...
...
@@ -1382,30 +1382,28 @@ is for this put the \fBsrun\fR command into a mode where various special
actions may be invoked.
.SH "MPI SUPPORT"
LAM/MPI version 7.0.4 or higher is well intergated with SLURM.
The \fBlamboot\fR command will acquire a SLURM resource allocation
and uses the \fBsrun\fR command to launch its \fBlamd\fR daemons on
each allocated node. See \fIhttp://www.lam\-mpi.org/\fR for more
information.
On computers with a Quadrics interconnect, \fBsrun\fR directly supports
the Quadrics version of MPI without modification. Applications build
using the Quadrics MPI library will communicate directly over the
Quadrics interconnect without any special \fBsrun\fR options.
Users may also use MPICH on any computer where that is available.
The \fBmpirun\fR command may need to be provided with information
on its command line identifying the resources to be used. The
installer of the MPICH software may configure it to perform these
steps automatically. At worst, you must specify two parameters:
.TP
\fB\-np SLURM_NPROCS\fR
number of processors to run on
.TP
\fB\-machinefile <machinefile>\fR
list of computers on which to execute. This list can be constructed
executing the command \fBsrun /bin/hostname\fR and writing its standard
output to the desired file. Execute \fBmpirun \-\-help\fR for more options.
MPI use depends upon the type of MPI being used.
There are three fundamentally different modes of operation used
by these various MPI implementation.
1. SLURM directly launches the tasks and performs initialization
of communications (Quadrics MPI, MPICH2, MPICH-GM, MVAPICH, MVAPICH2
and some MPICH1 modes). For example: "srun -n16 a.out".
2. SLURM creates a resource allocation for the job and then
mpirun launches tasks using SLURM's infrastructure (OpenMPI,
LAM/MPI, HP-MPI and some MPICH1 modes).
3. SLURM creates a resource allocation for the job and then
mpirun launches tasks using some mechanism other than SLURM,
such as SSH or RSH (BlueGene MPI and some MPICH1 modes).
These tasks initiated outside of SLURM's monitoring
or control. SLURM's epilog should be configured to purge
these tasks when the job's allocation is relinquished.
See \fIhttp://www.linux.gov/linux/slurm/quickstart.html#mpi\fR
for more information on use of these various MPI implementation
with SLURM.
.SH "MULTIPLE PROGRAM CONFIGURATION"
Comments in the configuration file must have a "#" in column one.
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment