Synopsis

int MPI_Start(MPI_Request *request)

Input/Output Parameters

request

communication request (handle)

Description

MPI_Start activates a persistent communication request that was created by an initialization procedure. The request argument is a handle returned by initialization procedures for persistent point-to-point, partitioned point-to-point, or persistent collective communication, and the associated request must be inactive. For a ready mode send request, a matching receive operation must be started before the call is made. The communication buffer must not be modified after the call until the operation completes. This call is local with semantics similar to the corresponding nonblocking communication operations.

A send operation started with MPI_Start can be matched with any receive operation, and a receive operation started with MPI_Start can receive messages generated by any send operation. Communication operations started from persistent requests are nonovertaking. If the same persistent communication request is used in concurrent threads, coordinating calls to ensure the correct sequence of Create, Start, Complete, and Free is the user’s responsibility.

Thread and Interrupt Safety

This routine is thread-safe. This means that this routine may be safely used by multiple threads without the need for any user-provided thread locks. However, the routine is not interrupt safe. Typically, this is due to the use of memory allocation routines such as 'malloc' or other non-MPICH runtime routines that are themselves not interrupt-safe.

Notes for Fortran

All MPI routines in Fortran (except for 'MPI_WTIME' and 'MPI_WTICK') have an additional argument 'ierr' at the end of the argument list. 'ierr' is an integer and has the same meaning as the return value of the routine in C. In Fortran, MPI routines are subroutines, and are invoked with the 'call' statement.

All MPI objects (e.g., 'MPI_Datatype', 'MPI_Comm') are of type 'INTEGER' in Fortran.

Errors

All MPI routines (except 'MPI_Wtime' and 'MPI_Wtick') return an error value; C routines as the value of the function and Fortran routines in the last argument. Before the value is returned, the current MPI error handler is called. By default, this error handler aborts the MPI job. The error handler may be changed with 'MPI_Comm_set_errhandler' (for communicators), 'MPI_File_set_errhandler' (for files), and 'MPI_Win_set_errhandler' (for RMA windows). The MPI-1 routine 'MPI_Errhandler_set' may be used but its use is deprecated. 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; however, MPI implementations will attempt to continue whenever possible.

  • MPI_SUCCESS - No error; MPI routine completed successfully.

  • MPI_ERR_REQUEST - Invalid 'MPI_Request'. Either null or, in the case of a 'MPI_Start' or 'MPI_Startall', not a persistent request.

  • MPI_ERR_OTHER - Other error; use 'MPI_Error_string' to get more information about this error code.