1MPI_Pack_size(3) LAM/MPI MPI_Pack_size(3)
2
6 MPI_Pack_size - Returns the upper bound on the amount of space needed
7 to pack a message
8
10 #include <mpi.h>
11 int MPI_Pack_size(int count, MPI_Datatype dtype,
12 MPI_Comm comm, int *psize)
13
15 count - count argument to packing call (integer)
16 dtype - datatype argument to packing call (handle)
17 comm - communicator argument to packing call (handle)
18
21 psize - upper bound on size of packed message, in bytes (integer)
22
25 The MPI standard document describes this in terms of MPI_Pack , but it
26 applies to both the MPI_Pack and MPI_Unpack functions. That is, the
27 value size is the maximum that is needed by either MPI_Pack or
28 MPI_Unpack .
29
33 All MPI routines in Fortran (except for MPI_WTIME and MPI_WTICK ) have
34 an additional argument ierr at the end of the argument list. ierr is
35 an integer and has the same meaning as the return value of the routine
36 in C. In Fortran, MPI routines are subroutines, and are invoked with
37 the call statement.
38 All MPI objects (e.g., MPI_Datatype , MPI_Comm ) are of type INTEGER in
40 Fortran.
41
44 If an error occurs in an MPI function, the current MPI error handler is
45 called to handle it. By default, this error handler aborts the MPI
46 job. The error handler may be changed with MPI_Errhandler_set ; the
47 predefined error handler MPI_ERRORS_RETURN may be used to cause error
48 values to be returned (in C and Fortran; this error handler is less
49 useful in with the C++ MPI bindings. The predefined error handler
50 MPI::ERRORS_THROW_EXCEPTIONS should be used in C++ if the error value
51 needs to be recovered). Note that MPI does not guarantee that an MPI
52 program can continue past an error.
53 All MPI routines (except MPI_Wtime and MPI_Wtick ) return an error
55 value; C routines as the value of the function and Fortran routines in
56 the last argument. The C++ bindings for MPI do not return error val‐
57 ues; instead, error values are communicated by throwing exceptions of
58 type MPI::Exception (but not by default). Exceptions are only thrown
59 if the error value is not MPI::SUCCESS .
60 Note that if the MPI::ERRORS_RETURN handler is set in C++, while MPI
63 functions will return upon an error, there will be no way to recover
64 what the actual error value was.
65 MPI_SUCCESS
66 - No error; MPI routine completed successfully.
67 MPI_ERR_COMM
68 - Invalid communicator. A common error is to use a null commu‐
69 nicator in a call (not even allowed in MPI_Comm_rank ).
70 MPI_ERR_COUNT
71 - Invalid count argument. Count arguments must be non-negative;
72 a count of zero is often valid.
73 MPI_ERR_TYPE
74 - Invalid datatype argument. May be an uncommitted MPI_Datatype
75 (see MPI_Type_commit ).
76 MPI_ERR_ARG
77 - Invalid argument. Some argument is invalid and is not identi‐
78 fied by a specific error class. This is typically a NULL
79 pointer or other such error.
80
83 MPI_Pack, MPI_Unpack
84
87 For more information, please see the official MPI Forum web site, which
88 contains the text of both the MPI-1 and MPI-2 standards. These docu‐
89 ments contain detailed information about each MPI function (most of
90 which is not duplicated in these man pages).
91 http://www.mpi-forum.org/
93
97 The LAM Team would like the thank the MPICH Team for the handy program
98 to generate man pages ("doctext" from ftp://ftp.mcs.anl.gov/pub/sow‐
99 ing/sowing.tar.gz ), the initial formatting, and some initial text for
100 most of the MPI-1 man pages.
101
103 packsize.c
104LAM/MPI 7.1.2 2/23/2006 MPI_Pack_size(3)