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
145c632f
Commit
145c632f
authored
11 years ago
by
Danny Auble
Browse files
Options
Downloads
Plain Diff
Merge remote-tracking branch 'origin/slurm-2.5'
parents
72dd23cc
a7f93a02
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/html/ibm-pe.shtml
+16
-21
16 additions, 21 deletions
doc/html/ibm-pe.shtml
with
16 additions
and
21 deletions
doc/html/ibm-pe.shtml
+
16
−
21
View file @
145c632f
...
...
@@ -422,27 +422,22 @@ For example:</p>
%_with_libnrt "/opt/ibmhpc/pecurrent/base/intel/lib64"
</pre>
<p>The poe command interacts with SLURM by loading a SLURM library providing
a variety of functions for its use. You must specify the location of that
library and note that SLURM is the workload manager in the file named
"/etc/poe.limits".
The library name is "libpermapi.so" and it is in installed with the other SLURM
libraries in the subdirectory "lib/slurm". A sample "/etc/poe.limits" file is
shown below. You will need to modify the value of MP_PE_RMLIB to match SLURM's
installation location on your system.<br>
<b>NOTE:</b> The poe command is loading and using the libpermapi.so library
initially from the /usr/lib64 directory. It later reads the /etc/poe.limits
file and loads the correct library. In order for poe to work with SLURM, it
needs to use the "libpermapi.so" generated by SLURM for all of its functions.
Until poe is modified to only load the correct library, it is necessary for
the file /usr/lib64/libpermapi.so to contain SLURM's library or a link to it.</p>
<pre>
#
# Sample /etc/poe.limits
# Modify the path below as appropriate
#
MP_PE_RMLIB=/usr/local/lib/slurm/libpermapi.so
</pre>
<p><b>IMPORTANT:</b>The poe command interacts with SLURM by loading a
SLURM library providing a variety of functions for its use. The
library name is <i>"libpermapi.so"</i> and it is in installed with the
other SLURM libraries in the subdirectory "lib/slurm". You must
modify the link of /usr/lib64/libpermapi.so to point to the location
of the slurm version of this library.</p>
<p>Modifying the "/etc/poe.limits" file is <b>not</b> enough. The poe
command is loading and using the libpermapi.so library initially
from the /usr/lib64 directory. It later reads the /etc/poe.limits
file and loads the library listed there. In order for poe to work
with SLURM, it needs to use the "libpermapi.so" generated by SLURM
for all of its functions. Until poe is modified to only load the
correct library, it is necessary for /usr/lib64/libpermapi.so to
contain SLURM's library or a link to it.</p>
<p>If you are having problems running on more than 32 nodes this is
most likely your issue.</p>
<p>Changes to the count of dynmamic switch windows necessitate cold-starting
Slurm (without jobs). The procedure is as follows:</p>
...
...
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