1MPI_Alloc_mem(3) LAM/MPI MPI_Alloc_mem(3)
2
3
4
6 MPI_Alloc_mem - Allocate memory for use by MPI message passing.
7
9 #include <mpi.h>
10 int MPI_Alloc_mem(MPI_Aint size, MPI_Info info, void *baseptr)
11
13 size - number of bytes to allocate
14 info - MPI_Info object
15
16
18 baseptr
19 - pointer to address of allocated memory
20
21
23 MPI_INFO_NULL is always valid for this function. For the TCP, SYSV,
24 and USYSV RPIs, the info argument is ignored, and this function is sim‐
25 ply a wrapper around malloc .
26
27
28 However, future RPIs (e.g., for Myrinet and VIA-based RPIs) will pro‐
29 vide "special" memory allocation routines that will allocate memory
30 that can be used directly for DMA.
31
32
34 All MPI routines in Fortran (except for MPI_WTIME and MPI_WTICK ) have
35 an additional argument ierr at the end of the argument list. ierr is
36 an integer and has the same meaning as the return value of the routine
37 in C. In Fortran, MPI routines are subroutines, and are invoked with
38 the call statement.
39
40 All MPI objects (e.g., MPI_Datatype , MPI_Comm ) are of type INTEGER in
41 Fortran.
42
43
45 If an error occurs in an MPI function, the current MPI error handler is
46 called to handle it. By default, this error handler aborts the MPI
47 job. The error handler may be changed with MPI_Errhandler_set ; the
48 predefined error handler MPI_ERRORS_RETURN may be used to cause error
49 values to be returned (in C and Fortran; this error handler is less
50 useful in with the C++ MPI bindings. The predefined error handler
51 MPI::ERRORS_THROW_EXCEPTIONS should be used in C++ if the error value
52 needs to be recovered). Note that MPI does not guarantee that an MPI
53 program can continue past an error.
54
55 All MPI routines (except MPI_Wtime and MPI_Wtick ) return an error
56 value; C routines as the value of the function and Fortran routines in
57 the last argument. The C++ bindings for MPI do not return error val‐
58 ues; instead, error values are communicated by throwing exceptions of
59 type MPI::Exception (but not by default). Exceptions are only thrown
60 if the error value is not MPI::SUCCESS .
61
62
63 Note that if the MPI::ERRORS_RETURN handler is set in C++, while MPI
64 functions will return upon an error, there will be no way to recover
65 what the actual error value was.
66 MPI_SUCCESS
67 - No error; MPI routine completed successfully.
68 MPI_ERR_ARG
69 - Invalid argument. Some argument is invalid and is not identi‐
70 fied by a specific error class. This is typically a NULL
71 pointer or other such error.
72 MPI_ERR_NO_MEM
73 - This error class is associated with an error code that indi‐
74 cates that free space is exhausted.
75
76
78 For more information, please see the official MPI Forum web site, which
79 contains the text of both the MPI-1 and MPI-2 standards. These docu‐
80 ments contain detailed information about each MPI function (most of
81 which is not duplicated in these man pages).
82
83 http://www.mpi-forum.org/
84
85
86
88 The LAM Team would like the thank the MPICH Team for the handy program
89 to generate man pages ("doctext" from ftp://ftp.mcs.anl.gov/pub/sow‐
90 ing/sowing.tar.gz ), the initial formatting, and some initial text for
91 most of the MPI-1 man pages.
92
94 allocmem.c
95
96
97
98LAM/MPI 7.1.2 2/23/2006 MPI_Alloc_mem(3)