Product specifications

Table Of Contents
5–Using QLogic MPI
QLogic MPI Limitations
5-26 IB6054601-00 H
S
The following features of QLogic MPI facilitate debugging:
Stack backtraces are provided for programs that crash.
The -debug and -debug-no-pause options are provided for mpirun.
These options make each node program start with debugging enabled. The
-debug option allows you to set breakpoints, and start running programs
individually. The -debug-no-pause option allows postmortem inspection.
Be sure to set -q 0 when using -debug.
Communication between mpirun and node programs can be printed by
specifying the mpirun
-verbose option.
MPI implementation debug messages can be printed by specifying the
mpirun -psc-debug-level option. This option can substantially impact
the performance of the node program.
Support is provided for progress timeout specifications, deadlock detection,
and generating information about where a program is stuck.
Several misconfigurations (such as mixed use of 32-bit/64-bit executables)
are detected by the runtime.
A formatted list containing information useful for high-level MPI application
profiling is provided by using the
-print-stats option with mpirun.
Statistics include minimum, maximum, and median values for message
transmission protocols as well as a more detailed information for expected
and unexpected message reception. See “MPI Stats” on page D-31 for more
information and a sample output listing.
QLogic MPI Limitations
The current version of QLogic MPI has the following limitations:
There are no C++ bindings to MPI; use the extern C MPI function calls.
In MPI-IO file I/O calls in the Fortran binding, offset, or displacement
arguments are limited to 32 bits. Thus, for example, the second argument of
MPI_File_seek must be between -2
31
and 2
31
-1, and the argument to
MPI_File_read_at must be between 0 and 2
32
-1.
NOTE:
The TotalView
®
debugger can be used with the Open MPI supplied in this
release. Consult the TotalView documentation for more information.