« Return to documentation listing
Table of Contents
#include <mpi.h> int MPI_Init_thread(int *argc, char ***argv, int required, int *provided)
USE MPI ! or the older form: INCLUDE ’mpif.h’ MPI_INIT_THREAD(REQUIRED, PROVIDED, IERROR) INTEGER REQUIRED, PROVIDED, IERROR
USE mpi_f08 MPI_Init_thread(required, provided, ierror) INTEGER, INTENT(IN) :: required INTEGER, INTENT(OUT) :: provided INTEGER, OPTIONAL, INTENT(OUT) :: ierror
MPI_Init_thread, as compared to MPI_Init, has a provision to request a certain level of thread support in required:
The level of thread support available to the program is set in provided, except in the C++ binding, where it is the return value of the function. In Open MPI, the value is dependent on how the library was configured and built. Note that there is no guarantee that provided will be greater than or equal to required.
Also note that calling MPI_Init_thread with a required value of MPI_THREAD_SINGLE is equivalent to calling MPI_Init.
All MPI programs must contain a call to MPI_Init or MPI_Init_thread. Open MPI accepts the C/C++ argc and argv arguments to main, but neither modifies, interprets, nor distributes them:
{
/* declare variables */
MPI_Init_thread(&argc, &argv, req, &prov);
/* parse arguments */
/* main program */
MPI_Finalize();
}
It is the caller’s responsibility to check the value of provided, as it may be less than what was requested in required.
The MPI Standard does not say what a program can do before an MPI_Init_thread or after an MPI_Finalize. In the Open MPI implementation, it should do as little as possible. In particular, avoid anything that changes the external state of the program, such as opening files, reading standard input, or writing to standard output.
shell$ ompi_info | grep "Thread support" Thread support: posix (MPI_THREAD_MULTIPLE: yes, OPAL support: yes, OMPI progress: no, Event lib: yes) shell$
The "MPI_THREAD_MULTIPLE: yes" portion of the above output indicates that Open MPI was compiled with MPI_THREAD_MULTIPLE support.
Note that there is a small performance penalty for using MPI_THREAD_MULTIPLE support; latencies for short messages will be higher as compared to when using MPI_THREAD_SINGLE, for example.
Before the error value is returned, the current MPI error handler is called. By default, this error handler aborts the MPI job, except for I/O function errors. The error handler may be changed with MPI_Comm_set_errhandler; the predefined error handler MPI_ERRORS_RETURN may be used to cause error values to be returned. Note that MPI does not guarantee that an MPI program can continue past an error.
MPI_Init MPI_Initialized MPI_Finalize MPI_Finalized