Synopsis
int MPI_Ialltoallw(const void *sendbuf, const int sendcounts[],
const int sdispls[], const MPI_Datatype sendtypes[],
void *recvbuf, const int recvcounts[], const int rdispls[],
const MPI_Datatype recvtypes[], MPI_Comm comm,
MPI_Request *request)
int MPI_Ialltoallw_c(const void *sendbuf, const MPI_Count sendcounts[],
const MPI_Aint sdispls[], const MPI_Datatype sendtypes[],
void *recvbuf, const MPI_Count recvcounts[],
const MPI_Aint rdispls[], const MPI_Datatype recvtypes[],
MPI_Comm comm, MPI_Request *request)
Input Parameters
- sendbuf
-
starting address of send buffer (choice)
- sendcounts
-
integer array (of length group size) specifying the number of elements to send to each rank (non-negative integer)
- sdispls
-
integer array (of length group size). Entry j specifies the displacement in bytes (relative to sendbuf) from which to take the outgoing data destined for process j (integer)
- sendtypes
-
array of datatypes (of length group size). Entry j specifies the type of data to send to process j (handle)
- recvcounts
-
integer array (of length group size) specifying the number of elements that can be received from each rank (non-negative integer)
- rdispls
-
integer array (of length group size). Entry i specifies the displacement in bytes (relative to recvbuf) at which to place the incoming data from process i (integer)
- recvtypes
-
array of datatypes (of length group size). Entry i specifies the type of data received from process i (handle)
- comm
-
communicator (handle)
Output Parameters
- recvbuf
-
address of receive buffer (choice)
- request
-
communication request (handle)
Description
MPI_Ialltoallw starts a nonblocking All-To-All collective operation that is the most general form of complete exchange, allowing separate specification of count, displacement, and datatype for each process pair.
If comm is an intra-communicator, the j-th block sent from process i is received by process j and placed in the i-th block of recvbuf, with displacements specified in bytes. The type signature associated with sendcounts[j] and sendtypes[j] at process i must equal the type signature associated with recvcounts[i] and recvtypes[i] at process j. If comm is an inter-communicator, each process in group A sends a message to each process in group B and vice versa. The in-place option for intra-communicators is specified by passing MPI_IN_PLACE to sendbuf at all processes, in which case sendcounts, sdispls, and sendtypes are ignored. All processes must call collective operations in the same order per communicator, and nonblocking collective operations do not match with blocking collective operations. Once initiated, send buffers and input argument arrays must not be modified and receive buffers must not be accessed until the operation completes. In multithreaded implementations, users must ensure the same communicator is not used concurrently by two different collective communication initialization calls at the same process.
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_ARG - Invalid argument. Some argument is invalid and is not identified by a specific error class (e.g., 'MPI_ERR_RANK').
-
MPI_ERR_BUFFER - Invalid buffer pointer. Usually a null buffer where one is not valid.
-
MPI_ERR_COMM - Invalid communicator. A common error is to use a null communicator in a call (not even allowed in 'MPI_Comm_rank').
-
MPI_ERR_COUNT - Invalid count argument. Count arguments must be non-negative; a count of zero is often valid.
-
MPI_ERR_TYPE - Invalid datatype argument. Additionally, this error can occur if an uncommitted MPI_Datatype (see 'MPI_Type_commit') is used in a communication call.
-
MPI_ERR_OTHER - Other error; use 'MPI_Error_string' to get more information about this error code.