Difference between revisions of "Must"
(Created page with "MUST can be used to detect and report MPI errors. __TOC__ == General == The MUST software consists of three individual packages: * P<sup>n</sup>MPI * GTI * MUST P<sup>n<...") |
|||
| Line 11: | Line 11: | ||
* MUST | * MUST | ||
| − | P<sup>n</sup>MPI is responsible for the basic infrastructure and collecting data by intercepting all MPI calls of the target application. GTI provides the tool structure and the MUST package | + | P<sup>n</sup>MPI is responsible for the basic infrastructure and collecting data by intercepting all MPI calls of the target application. GTI provides the tool structure and the MUST package performs the correctness checking. All three packages are configured and built together using [https://cmake.org/ CMake] and should only be used with the specific compiler and MPI library used in the process. |
| − | The two main | + | The two main use cases for MUST are during application development and porting of an application to a new system. MUST can single out new errors and those not manifesting in an application crash. It can also detect violations to the MPI standard on the target system. |
== Correctness Checking == | == Correctness Checking == | ||
| Line 25: | Line 25: | ||
* Operation usage | * Operation usage | ||
* Request usage | * Request usage | ||
| − | * Leak checks (MPI resources not freed before calling | + | * Leak checks (MPI resources not freed before calling MPI_Finalize) |
| − | * Type | + | * Type mismatches |
* Overlapping buffers passed to MPI | * Overlapping buffers passed to MPI | ||
* Deadlocks resulting from MPI calls | * Deadlocks resulting from MPI calls | ||
Revision as of 07:41, 10 January 2019
MUST can be used to detect and report MPI errors.
General
The MUST software consists of three individual packages:
- PnMPI
- GTI
- MUST
PnMPI is responsible for the basic infrastructure and collecting data by intercepting all MPI calls of the target application. GTI provides the tool structure and the MUST package performs the correctness checking. All three packages are configured and built together using CMake and should only be used with the specific compiler and MPI library used in the process.
The two main use cases for MUST are during application development and porting of an application to a new system. MUST can single out new errors and those not manifesting in an application crash. It can also detect violations to the MPI standard on the target system.
Correctness Checking
MUST provides checks for the following classes of errors:
- Constants and integer values
- Communicator usage
- Datatype usage
- Group usage
- Operation usage
- Request usage
- Leak checks (MPI resources not freed before calling MPI_Finalize)
- Type mismatches
- Overlapping buffers passed to MPI
- Deadlocks resulting from MPI calls
- Basic checks for thread level usage (MPI_Init_thread)
Scalability
The scalability of MUST is dependent on the scalibility of the application. So far, it has been successfully tested with up to 16000 parallel processors.
Usage
For installation instructions as well as the latest release please visit the project MUST website, where there is also a detailed documentation available.