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
A–mpirun Options Summary
Stats Options
A-4 IB6054601-00 H
S
-k, -kill-timeout seconds
This option indicates the time to wait for other ranks after the first rank exits.
Default: 60
-listen-addr <hostname>|<IPv4>
This option specifies which hostname (or IPv4 address) to listen on for incoming
socket connections. It is useful for an mpirun front-end multihomed host. By
default, mpirun assumes that ranks can independently resolve the hostname
obtained on the head node with gethostname(2). To change the default, put
this option in the global mpirun.defaults file or a user-local file.
-runscript
This is the script with which to run the node program.
-t, -timeout seconds
This option waits for specified time (in seconds) for each node to establish
connection back to mpirun. If seconds is -1 (negative one), mpirun will wait
indefinitely.
Default: 60
Stats Options
-M [=stats_types], -print-stats [=stats_types]
Statistics include minimum, maximum, and median values for message
transmission protocols as well as more detailed information for expected and
unexpected message reception. If the option is provided without an argument,
stats_types is assumed to be mpi.
The following stats_types can be specified:
One or more statistics types can be specified by separating them with a comma.
For example, -print-stats=ipath,counters displays InfiniPath
communication protocol as well as low-level device counter statistics. For details,
see “MPI Stats” on page D-31.
mpi
Shows an MPI-level summary (expected, unexpected message)
ipath
Shows a summary of InfiniPath interconnect communication
p2p
Shows detailed per-MPI rank communication information
counters
Shows low-level InfiniPath device counters
devstats.
Shows InfiniPath driver statistics
all
Shows statistics for all stats_types