HP-MPI Version 2.2 for Linux Release Note

HP-MPI V2.2 for Linux Release Note

What’s in This Version

In general, HP-MPI relies on applications terminating when they are sent SIGTERM.

Applications which intercept SIGTERM may not terminate properly.

Fast 1sided lock/unlock under VAPI

When using the VAPI protocol, HP-MPI 2.2 is able to use low-level hardware atomic

operations to provide a high performance and scalable 1sided lock/unlock implementation.

Note that 1sided lock/unlock is supported on all interconnects, but the performance will vary

depending on what kind of hardware support is available. See Table 3 on page 19 for more

information.

Scalability

HP-MPI 2.2 has been tested on InfiniBand clusters with as many as 2048 ranks using the

VAPI protocol. Most HP-MPI features function in a scalable manner. However, a few are still

subject to significant resource growth as the job size grows.

Table 3 Scalability

Feature

Affected

Interconnect/Protocol

Scalability Impact

spawn All

Forces use of pairwise socket connections

between all mpid’s (typically one mpid per

machine)

1sided

shared

lock/unlock

All except VAPI

Only VAPI provides low-level calls to

efficiently implement shared lock/unlock. All

other interconnects require mpid’s to satisfy

this feature.

1sided

exclusive

lock/unlock

All except VAPI and

ELAN

Both VAPI and ELAN provide low-level calls

which allow HP-MPI to efficiently implement

exclusive lock/unlock. All other interconnects

require mpid’s to satisfy this feature.

1sided other TCP/IP

All interconnects other than TCP/IP allow

HP-MPI to efficiently implement the

remainder of the 1sided functionality. Only

when using TCP/IP are mpid’s required to

satisfy this feature.