HP-MPI Version 2.3.1 for Linux Release Note
Table Of Contents
- HP-MPI V2.3.1 for Linux Release Note
- Table of Contents
- 1 Information About This Release
- 2 New or Changed Features in V2.3.1
- 3 New or Changed Features in V2.3
- 3.1 Options Supported Only on HP Hardware
- 3.2 System Check
- 3.3 Default Message Size Changed For -ndd
- 3.4 MPICH2 Compatibility
- 3.5 Support for Large Messages
- 3.6 Redundant License Servers
- 3.7 License Release/Regain on Suspend/Resume
- 3.8 Expanded Functionality for -ha
- 3.8.1 Support for High Availability on InfiniBand Verbs
- 3.8.2 Highly Available Infrastructure (-ha:infra)
- 3.8.3 Using MPI_Comm_connect and MPI_Comm_accept
- 3.8.4 Using MPI_Comm_disconnect
- 3.8.5 Instrumentation and High Availability Mode
- 3.8.6 Failure Recover (-ha:recover)
- 3.8.7 Network High Availability (-ha:net)
- 3.8.8 Failure Detection (-ha:detect)
- 3.8.9 Clarification of the Functionality of Completion Routines in High Availability Mode
- 3.9 Enhanced InfiniBand Support for Dynamic Processes
- 3.10 Singleton Launching
- 3.11 Using the -stdio=files Option
- 3.12 Using the -stdio=none Option
- 3.13 Expanded Lightweight Instrumentation
- 3.14 The api option to MPI_INSTR
- 3.15 New mpirun option -xrc
- 4 Known Issues and Workarounds
- 4.1 Running on iWarp Hardware
- 4.2 Running with Chelsio uDAPL
- 4.3 Mapping Ranks to a CPU
- 4.4 OFED Firmware
- 4.5 Spawn on Remote Nodes
- 4.6 Default Interconnect for -ha Option
- 4.7 Linking Without Compiler Wrappers
- 4.8 Locating the Instrumentation Output File
- 4.9 Using the ScaLAPACK Library
- 4.10 Increasing Shared Memory Segment Size
- 4.11 Using MPI_FLUSH_FCACHE
- 4.12 Using MPI_REMSH
- 4.13 Increasing Pinned Memory
- 4.14 Disabling Fork Safety
- 4.15 Using Fork with OFED
- 4.16 Memory Pinning with OFED 1.2
- 4.17 Upgrading to OFED 1.2
- 4.18 Increasing the nofile Limit
- 4.19 Using appfiles on HP XC Quadrics
- 4.20 Using MPI_Bcast on Quadrics
- 4.21 MPI_Issend Call Limitation on Myrinet MX
- 4.22 Terminating Shells
- 4.23 Disabling Interval Timer Conflicts
- 4.24 libpthread Dependency
- 4.25 Fortran Calls Wrappers
- 4.26 Bindings for C++ and Fortran 90
- 4.27 Using HP Caliper
- 4.28 Using -tv
- 4.29 Extended Collectives with Lightweight Instrumentation
- 4.30 Using -ha with Diagnostic Library
- 4.31 Using MPICH with Diagnostic Library
- 4.32 Using -ha with MPICH
- 4.33 Using MPI-2 with Diagnostic Library
- 4.34 Quadrics Memory Leak
- 5 Installation Information
- 6 Licensing Information
- 7 Additional Product Information
MPI_STDIO_OUTFILE and MPI_STDIO_ERRFILE. If these environment variables are
not set, /dev/null or NUL is used. In addition, these file specifications can include
the substrings %%, %h, %p, and %r, which are expanded to %, hostname, process
id, and rank number in MPI_COMM_WORLD. The files option causes the stdio options
p, r, and I to be ignored.
3.12 Using the -stdio=none Option
This option is equivalent to setting -stdio=files with MPI_STDIO_INFILE,
MPI_STDIO_OUTFILE and MPI_STDIO_ERRFILE all set to /dev/null or NUL.
3.13 Expanded Lightweight Instrumentation
This release extends HP-MPI lightweight instrumentation. Lightweight instrumentation
can be turned on by using either the -i option to mpirun or by setting the environment
variable MPI_INSTR.
HP-MPI lightweight instrumentation is now supported when using -ha:infra and
singletons. See “Singleton Launching” (page 22).
Instrumentation data now includes some information on messages sent to other MPI
worlds formed using MPI_Comm_accept(), MPI_Comm_connect(), or
MPI_Comm_join(). All off-world message data is accounted together using the
designation offw regardless of which off-world rank was involved in the
communication.
HP-MPI provides an API that enables users to access the lightweight instrumentation
data on a per-process basis before the application calling MPI_Finalize(). The
following declaration in C is necessary to access this functionality:
extern int hpmp_instrument_runtime(int reset)
A call to hpmp_instrument_runtime(0) populates the output file specified by the
-i option to mpirun or the MPI_INSTR environment variable with the statistics
available at the time of the call. Subsequent calls to hpmp_instrument_runtime()
or MPI_Finalize() will overwrite the contents of the specified file. A call to
hpmp_instrument_runtime(1) populates the file in the same way, but also resets
the statistics. If instrumentation is not being used, the call to
hpmp_instrument_runtime() has no effect.
3.14 The api option to MPI_INSTR
The api option to MPI_INSTR collects and prints detailed information about the MPI
Application Programming Interface (API). This option prints a new section in the
instrumentation output file for each MPI routine called by each rank. It contains the
MPI datatype and operation requested, along with message size, call counts, and timing
information.
The following is sample output from -I <file>:api on the example compute_pi.f:
3.12 Using the -stdio=none Option 23