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

5–Using QLogic MPI
MPD
IB6054601-00 H 5-23
A
The complete list of options is contained in Appendix A.
MPD
The Multi-Purpose Daemon (MPD) is an alternative to mpirun for launching MPI
jobs. It is described briefly in the following sections.
MPD Description
MPD was developed by Argonne National Laboratory (ANL) as part of the
MPICH-2 system. While the ANL MPD had some advantages over the use of their
mpirun (faster launching, better cleanup after crashes, better tolerance of node
failures), the QLogic mpirun offers the same advantages.
The disadvantage of MPD is reduced security, since it does not use ssh to launch
node programs. It is also more complex to use than mpirun because it requires
starting a ring of MPD daemons on the nodes. Therefore, QLogic recommends
using the normal mpirun mechanism for starting jobs, as described in the
previous chapter. However, if you want to use MPD, it is included in the InfiniPath
software.
Using MPD
To start an MPD environment, use the mpdboot program. You must provide
mpdboot with a file that lists the machines on which to run the mpd daemon. The
format of this file is the same as for the mpihosts file in the mpirun command.
Here is an example of how to run mpdboot:
$ mpdboot -f hostsfile
After mpdboot has started the MPD daemons, it will print a status message and
drop into a new shell.
To leave the MPD environment, exit from this shell. This will terminate the
daemons.
To use rsh instead of ssh with mpdboot, set the environment variable MPD_RSH
to the pathname of the desired remote shell. For example:
MPD_RSH=‘which rsh‘ mpdboot -n 16 -f hosts
To run an MPI program from within the MPD environment, use the mpirun
command. You do not need to provide an mpihosts file or a count of CPUs; by
default, mpirun uses all nodes and CPUs available within the MPD environment.
To check the status of the MPD daemons, use the mpdping command.