|
MPI_Alltoallv, MPI_Ialltoallv, MPI_Alltoallv_init - All processes send different amount of data to, and receive different amount of data from, all processes SYNTAXC Syntax#include <mpi.h> int MPI_Alltoallv(const void *sendbuf, const int sendcounts[], Fortran SyntaxUSE MPI ! or the older form: INCLUDE 'mpif.h' MPI_ALLTOALLV(SENDBUF, SENDCOUNTS, SDISPLS, SENDTYPE, Fortran 2008 SyntaxUSE mpi_f08 MPI_Alltoallv(sendbuf, sendcounts, sdispls, sendtype, recvbuf, recvcounts, INPUT PARAMETERS
OUTPUT PARAMETERS
DESCRIPTIONMPI_Alltoallv is a generalized collective operation in which all processes send data to and receive data from all other processes. It adds flexibility to MPI_Alltoall by allowing the user to specify data to send and receive vector-style (via a displacement and element count). The operation of this routine can be thought of as follows, where each process performs 2n (n being the number of processes in communicator comm) independent point-to-point communications (including communication with itself). MPI_Comm_size(comm, &n); for (i = 0, i < n; i++) Process j sends the k-th block of its local sendbuf to process k, which places the data in the j-th block of its local recvbuf. When a pair of processes exchanges data, each may pass different element count and datatype arguments so long as the sender specifies the same amount of data to send (in bytes) as the receiver expects to receive. Note that process i may send a different amount of data to process j than it receives from process j. Also, a process may send entirely different amounts of data to different processes in the communicator. WHEN COMMUNICATOR IS AN INTER-COMMUNICATOR When the communicator is an inter-communicator, the gather operation occurs in two phases. The data is gathered from all the members of the first group and received by all the members of the second group. Then the data is gathered from all the members of the second group and received by all the members of the first. The operation exhibits a symmetric, full-duplex behavior. The first group defines the root process. The root process uses MPI_ROOT as the value of root. All other processes in the first group use MPI_PROC_NULL as the value of root. All processes in the second group use the rank of the root process in the first group as the value of root. When the communicator is an intra-communicator, these groups are the same, and the operation occurs in a single phase. USE OF IN-PLACE OPTIONWhen the communicator is an intracommunicator, you can perform an all-to-all operation in-place (the output buffer is used as the input buffer). Use the variable MPI_IN_PLACE as the value of sendbuf. In this case, sendcounts, sdispls, and sendtype are ignored. The input data of each process is assumed to be in the area where that process would receive its own contribution to the receive buffer. NOTESThe specification of counts and displacements should not cause any location to be written more than once. All arguments on all processes are significant. The comm argument, in particular, must describe the same communicator on all processes. The offsets of sdispls and rdispls are measured in units of sendtype and recvtype, respectively. Compare this to MPI_Alltoallw, where these offsets are measured in bytes. 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
|