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
application runs the system check tests. When the system checks are completed, the
application exits. This allows the normal application launch procedure to be used
during the test, including any job schedulers, wrapper scripts, and local environment
settings.
By default, the HPMPI_SYSTEM_CHECK API cannot be used if MPI_Init has already
been called, and the API will call MPI_Finalize before returning.
3.3 Default Message Size Changed For -ndd
When deferred deregistration is used, pinning memory is fast. Therefore, the default
setting for MPI_RDMA_MSGSIZE is 16384, 16384, 4194304 which means any message
over 16384 bytes is pinned for direct use in RDMA operations.
However, if deferred deregistration is not used (-ndd), then pinning memory is
expensive. In that case, the default setting for MPI_RDMA_MSGSIZE is 16384, 262144,
4194304 which means messages larger than 16384 and smaller than or equal to 262144
bytes are copied into pre-pinned memory using HP-MPI middle message protocol
rather than being pinned and used in RDMA operations directly.
The middle message protocol performs better than the long message protocol if deferred
deregistration is not used.
For more information, see the MPI_RDMA_MSGSIZE section of the mpienv manpage.
3.4 MPICH2 Compatibility
This release enhances MPICH compatibility mode by supporting applications and
libraries that use the MPICH2 implementation. MPICH2 is not a standard, but rather
a specific implementation of the MPI-2.1 standard. HP-MPI provides MPICH2
compatibility with the following wrappers:
Table 3-1 MPICH Wrappers
MPICH2MPICH1
mpirun.mpich2mpirun.mpich
mpicc.mpich2mpicc.mpich
mpif77.mpich2mpif77.mpich
mpif90.mpich2mpif90.mpich
Object files built with HP-MPI MPICH compiler wrappers can be used by an application
that uses the MPICH implementation. You must relink applications built using MPICH
compliant libraries to use HP-MPI in MPICH compatibility mode.
14 New or Changed Features in V2.3