Product specifications

F–Useful Programs and Files
Summary and Descriptions of Useful Programs
F-12 IB6054601-00 H
S
mpirun
mpirun determines whether the program is being run against a QLogic or
non-QLogic driver. It is installed from the mpi-frontend RPM. Sample
commands and results are shown in the following paragraphs.
QLogic-built:
$ mpirun -np 2 -m /tmp/id1 -d0x101 mpi_latency 1 0
asus-01:0.ipath_setaffinity: Set CPU affinity to 1, port 0:2:0
(1 active chips)
asus-01:0.ipath_userinit: Driver is QLogic-built
Non-QLogic built:
$ mpirun -np 2 -m /tmp/id1 -d0x101 mpi_latency 1 0
asus-01:0.ipath_setaffinity: Set CPU affinity to 1, port 0:2:0
(1 active chips)
asus-01:0.ipath_userinit: Driver is not QLogic-built
mpi_stress
This is an MPI stress test program designed to load up an MPI interconnect with
point-to-point messages while optionally checking for data integrity. By default, it
runs with all-to-all traffic patterns, optionally including oneself and one’s local
shared memory (shm) peers. It can also be set up with multi-dimensional grid
traffic patterns; this can be parameterized to run rings, open 2D grids, closed
2D grids, cubic lattices, hypercubes, and so on.
Optionally, the message data can be randomized and checked using CRC
checksums (strong but slow) or XOR checksums (weak but fast). The
communication kernel is built out of non-blocking point-to-point calls to load up the
interconnect. The program is not designed to exhaustively test out different MPI
primitives. Performance metrics are displayed, but should be carefully interpreted
in terms of the features enabled.
This is an MPI application and should be run under mpirun or its equivalent.
The following example runs 16 processes and a specified hosts file using the
default options (all-to-all connectivity, 64 to 4MB messages in powers of two, one
iteration, no data integrity checking):
$ mpirun -np 16 -m hosts mpi_stress
There are a number of options for mpi_stress ; this one may be particularly useful:
-P
This option poisons receive buffers at initialization and after each receive;
pre-initialize with random data so that any parts that are not being correctly
updated with received data can be observed later.
See the mpi_stress(1) man page for more information.