MPI_Irsend - Starts a ready-mode nonblocking send.
184.108.40.206.1. C Syntax
#include <mpi.h> int MPI_Irsend(const void *buf, int count, MPI_Datatype datatype, int dest, int tag, MPI_Comm comm, MPI_Request *request)
220.127.116.11.2. Fortran Syntax
USE MPI ! or the older form: INCLUDE 'mpif.h' MPI_IRSEND(BUF, COUNT, DATATYPE, DEST, TAG, COMM, REQUEST, IERROR) <type> BUF(*) INTEGER COUNT, DATATYPE, DEST, TAG, COMM, REQUEST, IERROR
18.104.22.168.3. Fortran 2008 Syntax
USE mpi_f08 MPI_Irsend(buf, count, datatype, dest, tag, comm, request, ierror) TYPE(*), DIMENSION(..), INTENT(IN), ASYNCHRONOUS :: buf INTEGER, INTENT(IN) :: count, dest, tag TYPE(MPI_Datatype), INTENT(IN) :: datatype TYPE(MPI_Comm), INTENT(IN) :: comm TYPE(MPI_Request), INTENT(OUT) :: request INTEGER, OPTIONAL, INTENT(OUT) :: ierror
22.214.171.124. INPUT PARAMETERS
buf: Initial address of send buffer (choice).
count: Number of elements in send buffer (integer).
datatype: Datatype of each send buffer element (handle).
dest: Rank of destination (integer).
tag: Message tag (integer).
comm: Communicator (handle).
126.96.36.199. OUTPUT PARAMETERS
request: Communication request (handle).
IERROR: Fortran only: Error status (integer).
MPI_Irsend starts a ready-mode nonblocking send. Nonblocking calls allocate a communication request object and associate it with the request handle (the argument request). The request can be used later to query the status of the communication or to wait for its completion.
A nonblocking send call indicates that the system may start copying data out of the send buffer. The sender should not modify any part of the send buffer after a nonblocking send operation is called, until the send completes.
Almost all MPI routines return an error value; C routines as the return result of the function and Fortran routines in the last argument.
Before the error value is returned, the current MPI error handler associated with the communication object (e.g., communicator, window, file) is called. If no communication object is associated with the MPI call, then the call is considered attached to MPI_COMM_SELF and will call the associated MPI error handler. When MPI_COMM_SELF is not initialized (i.e., before MPI_INIT / MPI_INIT_THREAD, after MPI_FINALIZE, or when using the Sessions Model exclusively) the error raises the initial error handler. The initial error handler can be changed by calling MPI_COMM_SET_ERRHANDLER on MPI_COMM_SELF when using the World model, or the mpi_initial_errhandler CLI argument to mpiexec or info key to MPI_COMM_SPAWN[_MULTIPLE]. If no other appropriate error handler has been set, then the MPI_ERRORS_RETURN error handler is called for MPI I/O functions and the MPI_ERRORS_ABORT error handler is called for all other MPI functions.
In the sessions model, the error handler can be set during MPI_Session_init.
Open MPI includes three predefined error handlers that can be used:
MPI_ERRORS_ARE_FATAL: Causes the program to abort all connected MPI processes. MPI_ERRORS_ABORT: An error handler that can be invoked on a communicator, window, file, or session. When called on a communicator, it acts as if MPI_ABORT was called on that communicator. If called on a window or file, acts as if MPI_ABORT was called on a communicator containing the group of processes in the corresponding window or file. If called on a session, aborts only the local process. MPI_ERRORS_RETURN: Returns an error code to the application.
MPI applications can also implement their own error handlers.
Note that MPI does not guarantee that an MPI program can continue past an error.
See the MPI man page for a full list of MPI error codes.
See the Error Handling section of the MPI-3 standard for more information.