|
MPI_Isendrecv — Sends and receives a message. SYNTAXC Syntax#include <mpi.h> int MPI_Isendrecv(const void *sendbuf, int sendcount, MPI_Datatype sendtype, Fortran SyntaxUSE MPI ! or the older form: INCLUDE 'mpif.h' MPI_ISENDRECV(SENDBUF, SENDCOUNT, SENDTYPE, DEST, SENDTAG, Fortran 2008 SyntaxUSE mpi_f08 MPI_Isendrecv(sendbuf, sendcount, sendtype, dest, sendtag, recvbuf, INPUT PARAMETERS
OUTPUT PARAMETERS
DESCRIPTIONThe non-blocking send-receive operations combine in one call the sending of a message to one destination and the receiving of another message, from another process. The two (source and destination) are possibly the same. This operation is useful for executing a shift operation across a chain of processes. The send-receive operation can be used in conjunction with the functions described in the “Process Topologies” chapter of the MPI Standard in order to perform shifts on various logical topologies. A message sent by a send-receive operation can be received by a regular receive operation or probed by a probe operation; a send-receive operation can receive a message sent by a regular send operation. MPI_Isendrecv executes a non-blocking send and receive operation. Both send and receive use the same communicator, but possibly different tags. The send buffer and receive buffers must be disjoint, and may have different lengths and datatypes. A non-blocking send-receive request can be determined to be completed by calling the MPI_Wait, MPI_Waitany, MPI_Test, or MPI_Testany with the request returned by this function. ERRORSAlmost 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/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. Open MPI includes three predefined error handlers that can be used:
MPI applications can also implement their own error handlers by calling:
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.1 standard for more information. SEE ALSO:
COPYRIGHT2003-2025, The Open MPI Community
|