1MPI_Alltoallv(3) LAM/MPI MPI_Alltoallv(3)
2
6 MPI_Alltoallv - Sends data from all to all processes, with a displace‐
7 ment
8
10 #include <mpi.h>
11 int MPI_Alltoallv(void *sbuf, int *scounts, int *sdisps,
12 MPI_Datatype sdtype, void *rbuf, int *rcounts,
13 int *rdisps, MPI_Datatype rdtype,
14 MPI_Comm comm)
15
17 sbuf - starting address of send buffer (choice)
18 scounts
19 - integer array equal to the group size specifying the number of
20 elements to send to each processor
21 sdisps - integer array (of length group size). Entry j specifies the
22 displacement (relative to sendbuf from which to take the outgo‐
23 ing data destined for process j
24 sdtype - data type of send buffer elements (handle)
26 rcounts
27 - integer array equal to the group size specifying the maximum
28 number of elements that can be received from each processor
29 rdisps - integer array (of length group size). Entry i specifies the
30 displacement (relative to recvbuf at which to place the incom‐
31 ing data from process i
32 rdtype - data type of receive buffer elements (handle)
34 comm - communicator (handle)
35
38 rbuf - address of receive buffer (choice)
39
42 The receive buffer rbuf needs to be large enough to hold the data that
43 will be received from all processes.
44
47 LAM/MPI does not yet support invoking this function on a communicator
48 that contains ranks that are non-local IMPI procs.
49
52 All MPI routines in Fortran (except for MPI_WTIME and MPI_WTICK ) have
53 an additional argument ierr at the end of the argument list. ierr is
54 an integer and has the same meaning as the return value of the routine
55 in C. In Fortran, MPI routines are subroutines, and are invoked with
56 the call statement.
57 All MPI objects (e.g., MPI_Datatype , MPI_Comm ) are of type INTEGER in
59 Fortran.
60
63 If an error occurs in an MPI function, the current MPI error handler is
64 called to handle it. By default, this error handler aborts the MPI
65 job. The error handler may be changed with MPI_Errhandler_set ; the
66 predefined error handler MPI_ERRORS_RETURN may be used to cause error
67 values to be returned (in C and Fortran; this error handler is less
68 useful in with the C++ MPI bindings. The predefined error handler
69 MPI::ERRORS_THROW_EXCEPTIONS should be used in C++ if the error value
70 needs to be recovered). Note that MPI does not guarantee that an MPI
71 program can continue past an error.
72 All MPI routines (except MPI_Wtime and MPI_Wtick ) return an error
74 value; C routines as the value of the function and Fortran routines in
75 the last argument. The C++ bindings for MPI do not return error val‐
76 ues; instead, error values are communicated by throwing exceptions of
77 type MPI::Exception (but not by default). Exceptions are only thrown
78 if the error value is not MPI::SUCCESS .
79 Note that if the MPI::ERRORS_RETURN handler is set in C++, while MPI
82 functions will return upon an error, there will be no way to recover
83 what the actual error value was.
84 MPI_ERR_COMM
85 - Invalid communicator. A common error is to use a null commu‐
86 nicator in a call (not even allowed in MPI_Comm_rank ).
87 MPI_ERR_OTHER
88 - A collective implementation was not able to be located at run-
89 time for this communicator.
90 MPI_ERR_OTHER
91 - A communicator that contains some non-local IMPI procs was
92 used for some function which has not yet had the IMPI extensions
93 implemented yet. For example, most collectives on IMPI communi‐
94 cators have not been implemented yet.
95 MPI_ERR_COUNT
96 - Invalid count argument. Count arguments must be non-negative;
97 a count of zero is often valid.
98 MPI_ERR_TYPE
99 - Invalid datatype argument. May be an uncommitted MPI_Datatype
100 (see MPI_Type_commit ).
101 MPI_ERR_BUFFER
102 - Invalid buffer pointer. Usually a null buffer where one is
103 not valid.
104
107 For more information, please see the official MPI Forum web site, which
108 contains the text of both the MPI-1 and MPI-2 standards. These docu‐
109 ments contain detailed information about each MPI function (most of
110 which is not duplicated in these man pages).
111 http://www.mpi-forum.org/
113
117 The LAM Team would like the thank the MPICH Team for the handy program
118 to generate man pages ("doctext" from ftp://ftp.mcs.anl.gov/pub/sow‐
119 ing/sowing.tar.gz ), the initial formatting, and some initial text for
120 most of the MPI-1 man pages.
121
123 alltoallv.c
124LAM/MPI 7.1.2 2/23/2006 MPI_Alltoallv(3)