source: proiecte/hpl/openmpi_compiled/share/man/man3/MPI_Waitall.3 @ 97

Last change on this file since 97 was 97, checked in by (none), 14 years ago

Adding compiled files

File size: 4.5 KB
Line 
1.\"Copyright 2006-2008 Sun Microsystems, Inc.
2.\" Copyright (c) 1996 Thinking Machines Corporation
3.TH MPI_Waitall 3 "Dec 08, 2009" "1.4" "Open MPI"
4.SH NAME
5\fBMPI_Waitall\fP \- Waits for all given communications to complete.
6
7.SH SYNTAX
8.ft R
9.SH C Syntax
10.nf
11#include <mpi.h>
12int MPI_Waitall(int \fIcount\fP, MPI_Request\fI *array_of_requests\fP,
13        MPI_Status \fI*array_of_statuses\fP)
14
15.SH Fortran Syntax
16.nf
17INCLUDE 'mpif.h'
18MPI_WAITALL(\fICOUNT, ARRAY_OF_REQUESTS, ARRAY_OF_STATUSES, IERROR\fP)
19        INTEGER \fICOUNT, ARRAY_OF_REQUESTS(*)\fP
20        INTEGER \fIARRAY_OF_STATUSES(MPI_STATUS_SIZE,*), IERROR\fP
21
22.SH C++ Syntax
23.nf
24#include <mpi.h>
25static void Request::Waitall(int \fIcount\fP, Request \fIarray_of_requests\fP[],
26        Status \fIarray_of_statuses\fP[])
27
28static void Request::Waitall(int \fIcount\fP, Request \fIarray_of_requests\fP[])
29
30.SH INPUT PARAMETERS
31.ft R
32.TP 1i
33count     
34Lists length (integer).
35.TP 1i
36array_of_requests
37Array of requests (array of handles).
38.sp
39.SH OUTPUT PARAMETERS
40.ft R
41.TP 1i
42array_of_statuses
43Array of status objects (array of status).
44.ft R
45.TP 1i
46IERROR
47Fortran only: Error status (integer).
48
49.SH DESCRIPTION
50.ft R
51Blocks until all communication operations associated with active handles in the list complete, and returns the status of all these operations (this includes the case where no handle in the list is active). Both arrays have the same number of valid entries. The ith entry in array_of_statuses is set to the return status of the ith operation. Requests that were created by nonblocking communication operations are deallocated, and the corresponding handles in the array are set to MPI_REQUEST_NULL. The list may contain null or inactive handles. The call sets to empty the status of each such entry.
52.sp
53The error-free execution of MPI_Waitall(count, array_of_requests, array_of_statuses) has the same effect as the execution of  MPI_Wait(&array_of_request[i], &array_of_statuses[i]), for i=0,...,count-1, in some arbitrary order. MPI_Waitall with an array of length 1 is equivalent to MPI_Wait.
54.sp
55When one or more of the communications completed by a call to MPI_Waitall fail, it is desirable to return specific information on each communication. The function MPI_Waitall will return in such case the error code MPI_ERR_IN_STATUS and will set the error field of each status to a specific error code. This code will be MPI_SUCCESS if the specific communication completed; it will be another specific error code if it failed; or it can be MPI_ERR_PENDING if it has neither failed nor completed. The function MPI_Waitall will return MPI_SUCCESS if no request had an error, or will return another error code if it failed for other reasons (such as invalid arguments). In such cases, it will not update the error fields of the statuses.
56.sp
57If your application does not need to examine the \fIarray_of_statuses\fP field, you can save resources by using the predefined constant MPI_STATUSES_IGNORE can be used as a special value for the \fIarray_of_statuses\fP argument.
58
59.SH ERRORS
60For each invocation of MPI_Waitall, if one or more requests generate
61an MPI exception, only the \fIfirst\fP MPI request that caused an
62exception will be passed to its corresponding error handler.  No other
63error handlers will be invoked (even if multiple requests generated
64exceptions).  However, \fIall\fP requests that generate an exception
65will have a relevant error code set in the corresponding
66status.MPI_ERROR field (unless MPI_IGNORE_STATUSES was used).
67.sp
68The default error handler aborts the MPI job, except for I/O function
69errors. The error handler may be changed with MPI_Comm_set_errhandler,
70MPI_File_set_errhandler, or MPI_Win_set_errhandler (depending on the
71type of MPI handle that generated the MPI request); the predefined
72error handler MPI_ERRORS_RETURN may be used to cause error values to
73be returned. Note that MPI does not guarantee that an MPI program can
74continue past an error.
75.sp
76If the invoked error handler allows MPI_Waitall to return to the
77caller, the value MPI_ERR_IN_STATUS will be returned in the C and
78Fortran bindings.  In C++, if the predefined error handler
79MPI::ERRORS_THROW_EXCEPTIONS is used, the value MPI::ERR_IN_STATUS
80will be contained in the MPI::Exception object.  The MPI_ERROR field
81can then be examined in the array of returned statuses to determine
82exactly which request(s) generated an exception.
83
84.SH SEE ALSO
85.ft R
86.sp
87MPI_Comm_set_errhandler
88.br
89MPI_File_set_errhandler
90.br
91MPI_Test
92.br
93MPI_Testall
94.br
95MPI_Testany
96.br
97MPI_Testsome
98.br
99MPI_Wait
100.br
101MPI_Waitany
102.br
103MPI_Waitsome
104.br
105MPI_Win_set_errhandler
106.br
107
Note: See TracBrowser for help on using the repository browser.