<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML3.2 EN">
<HTML>
<HEAD>
<META NAME="GENERATOR" CONTENT="DOCTEXT">
<TITLE>MPI_Ialltoallw</TITLE>
</HEAD>
<BODY BGCOLOR="FFFFFF">
<H1 id="MPI_Ialltoallw">MPI_Ialltoallw</H1>
Nonblocking generalized all-to-all communication allowing different datatypes, counts, and displacements for each partner
<H2>Synopsis</H2>
<PRE>
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)
</PRE>
<H2>Input Parameters</H2>
<DL>
<DT><B>sendbuf </B> <DD> starting address of the send buffer (choice)
<DT><B>sendcounts </B> <DD> non-negative integer array (of length group size) specifying the number of elements to send to each processor
<DT><B>sdispls </B> <DD> integer array (of length group size). Entry j specifies the displacement relative to sendbuf from which to take the outgoing data destined for process j
<DT><B>sendtypes </B> <DD> array of datatypes (of length group size). Entry j specifies the type of data to send to process j (array of handles)
<DT><B>recvcounts </B> <DD> non-negative integer array (of length group size) specifying the number of elements that can be received from each processor
<DT><B>rdispls </B> <DD> integer array (of length group size). Entry i specifies the displacement relative to recvbuf at which to place the incoming data from process i
<DT><B>recvtypes </B> <DD> array of datatypes (of length group size). Entry i specifies the type of data received from process i (array of handles)
<DT><B>comm </B> <DD> communicator (handle)
</DL>
<P>
<H2>Output Parameters</H2>
<DL>
<DT><B>recvbuf </B> <DD> starting address of the receive buffer (choice)
<DT><B>request </B> <DD> communication request (handle)
</DL>
<P>
<H2>Thread and Interrupt Safety</H2>
<P>
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 <tt>malloc
</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
<P>
<H2>Notes for Fortran</H2>
All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
an additional argument <tt>ierr</tt> at the end of the argument list. <tt>ierr
</tt>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
<tt>call</tt> statement.
<P>
All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
</tt>in Fortran.
<P>
<H2>Errors</H2>
<P>
All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
RMA windows). The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
its use is deprecated. The predefined error handler
<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
Note that MPI does <em>not</em> guarentee that an MPI program can continue past
an error; however, MPI implementations will attempt to continue whenever
possible.
<P>
</BODY></HTML>