« Return to documentation listing
Table of Contents
MPI_Rsend_init - Builds a handle for a ready send.
#include <mpi.h>
int MPI_Rsend_init(void *buf, int count, MPI_Datatype datatype,
int dest, int tag, MPI_Comm comm, MPI_Request *request)
INCLUDE ’mpif.h’
MPI_RSEND_INIT(BUF, COUNT, DATATYPE, DEST, TAG, COMM, REQUEST,
IERROR)
<type> BUF(*)
INTEGER COUNT, DATATYPE, DEST, TAG, COMM, REQUEST, IERROR
#include <mpi.h>
Prequest Comm::Rsend_init(const void* buf, int count, const
Datatype& datatype, int dest, int tag) const
- buf
- Initial address of send buffer (choice).
- count
- Number
of elements sent (integer).
- datatype
- Type of each element (handle).
- dest
- Rank of destination (integer).
- tag
- Message tag (integer).
- comm
- Communicator
(handle).
- request
- Communication request (handle).
- IERROR
- Fortran only: Error status (integer).
Creates a persistent
communication object for a ready mode send operation, and binds to it all
the arguments of a send operation.
A communication (send or receive) that
uses a persistent request is initiated by the function MPI_Start.
Almost
all MPI routines return an error value; C routines as the value of the
function and Fortran routines in the last argument. C++ functions do not
return errors. If the default error handler is set to MPI::ERRORS_THROW_EXCEPTIONS,
then on error the C++ exception mechanism will be used to throw an MPI:Exception
object.
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_Bsend_init
MPI_Send_init
MPI_Sssend_init
MPI_Recv_init
MPI_Start
MPI_Startall
MPI_Request_free
Table of Contents
« Return to documentation listing
|