Product specifications
Table Of Contents
- Table of Contents
- 1 Introduction
- 2 Feature Overview
- 3 Step-by-Step Cluster Setup and MPI Usage Checklists
- 4 InfiniPath Cluster Setup and Administration
- Introduction
- Installed Layout
- Memory Footprint
- BIOS Settings
- InfiniPath and OpenFabrics Driver Overview
- OpenFabrics Drivers and Services Configuration and Startup
- Other Configuration: Changing the MTU Size
- Managing the InfiniPath Driver
- More Information on Configuring and Loading Drivers
- Performance Settings and Management Tips
- Host Environment Setup for MPI
- Checking Cluster and Software Status
- 5 Using QLogic MPI
- Introduction
- Getting Started with MPI
- QLogic MPI Details
- Use Wrapper Scripts for Compiling and Linking
- Configuring MPI Programs for QLogic MPI
- To Use Another Compiler
- Process Allocation
- mpihosts File Details
- Using mpirun
- Console I/O in MPI Programs
- Environment for Node Programs
- Environment Variables
- Running Multiple Versions of InfiniPath or MPI
- Job Blocking in Case of Temporary InfiniBand Link Failures
- Performance Tuning
- MPD
- QLogic MPI and Hybrid MPI/OpenMP Applications
- Debugging MPI Programs
- QLogic MPI Limitations
- 6 Using Other MPIs
- A mpirun Options Summary
- B Benchmark Programs
- C Integration with a Batch Queuing System
- D Troubleshooting
- Using LEDs to Check the State of the Adapter
- BIOS Settings
- Kernel and Initialization Issues
- OpenFabrics and InfiniPath Issues
- Stop OpenSM Before Stopping/Restarting InfiniPath
- Manual Shutdown or Restart May Hang if NFS in Use
- Load and Configure IPoIB Before Loading SDP
- Set $IBPATH for OpenFabrics Scripts
- ifconfig Does Not Display Hardware Address Properly on RHEL4
- SDP Module Not Loading
- ibsrpdm Command Hangs when Two Host Channel Adapters are Installed but Only Unit 1 is Connected to the Switch
- Outdated ipath_ether Configuration Setup Generates Error
- System Administration Troubleshooting
- Performance Issues
- QLogic MPI Troubleshooting
- Mixed Releases of MPI RPMs
- Missing mpirun Executable
- Resolving Hostname with Multi-Homed Head Node
- Cross-Compilation Issues
- Compiler/Linker Mismatch
- Compiler Cannot Find Include, Module, or Library Files
- Problem with Shell Special Characters and Wrapper Scripts
- Run Time Errors with Different MPI Implementations
- Process Limitation with ssh
- Number of Processes Exceeds ulimit for Number of Open Files
- Using MPI.mod Files
- Extending MPI Modules
- Lock Enough Memory on Nodes When Using a Batch Queuing System
- Error Creating Shared Memory Object
- gdb Gets SIG32 Signal Under mpirun -debug with the PSM Receive Progress Thread Enabled
- General Error Messages
- Error Messages Generated by mpirun
- MPI Stats
- E Write Combining
- F Useful Programs and Files
- G Recommended Reading
- Glossary
- Index

C–Integration with a Batch Queuing System
Lock Enough Memory on Nodes when Using SLURM
IB6054601-00 H C-5
A
The following command terminates all processes using the QLogic interconnect:
# /sbin/fuser -k /dev/ipath
For more information, see the man pages for fuser(1) and lsof(8).
Note that hard and explicit program termination, such as kill -9 on the mpirun
Process ID (PID), may result in QLogic MPI being unable to guarantee that the
/dev/shm shared memory file is properly removed. As many stale files
accumulate on each node, an error message can appear at startup:
node023:6.Error creating shared memory object in shm_open(/dev/shm
may have stale shm files that need to be removed):
If this occurs, administrators should clean up all stale files by using this command:
# rm -rf /dev/shm/psm_shm.*
See “Error Creating Shared Memory Object” on page D-24 for more information.
Lock Enough Memory on Nodes when Using
SLURM
This section is identical to information provided in “Lock Enough Memory on
Nodes When Using a Batch Queuing System” on page D-23. It is repeated here
for your convenience.
QLogic MPI requires the ability to lock (pin) memory during data transfers on each
compute node. This is normally done via /etc/initscript, which is created or
modified during the installation of the infinipath RPM (setting a limit of
128 MB, with the command ulimit -l 131072).
Some batch systems, such as SLURM, propagate the user’s environment from
the node where you start the job to all the other nodes. For these batch systems,
you may need to make the same change on the node from which you start your
batch jobs.
If this file is not present or the node has not been rebooted after the infinipath
RPM has been installed, a failure message similar to one of the following will be
generated.
The following message displays during installation:
$ mpirun -np 2 -m ~/tmp/sm mpi_latency 1000 1000000
iqa-19:0.ipath_userinit: mmap of pio buffers at 100000 failed:
Resource temporarily unavailable
iqa-19:0.Driver initialization failure on /dev/ipath
iqa-20:1.ipath_userinit: mmap of pio buffers at 100000 failed:
Resource temporarily unavailable
iqa-20:1.Driver initialization failure on /dev/ipath