1MPI_Comm_get_attr(3) LAM/MPI MPI_Comm_get_attr(3)
2
6 MPI_Comm_get_attr - Get communicator attribute value
7
9 #include <mpi.h>
10 int
11 MPI_Comm_get_attr(MPI_Comm comm, int key, void *value, int *found)
12
14 comm - Communicator to which attribute is attached
15 key - key value
16
19 value - attribute value, unless found = false
20 found - false if no attribute is associated with the key
21
24 The IMPI standard only supports MPI-1 functions. Hence, this function
25 is currently not designed to operate within an IMPI job.
26
29 All MPI routines in Fortran (except for MPI_WTIME and MPI_WTICK ) have
30 an additional argument ierr at the end of the argument list. ierr is
31 an integer and has the same meaning as the return value of the routine
32 in C. In Fortran, MPI routines are subroutines, and are invoked with
33 the call statement.
34 All MPI objects (e.g., MPI_Datatype , MPI_Comm ) are of type INTEGER in
36 Fortran.
37
40 If an error occurs in an MPI function, the current MPI error handler is
41 called to handle it. By default, this error handler aborts the MPI
42 job. The error handler may be changed with MPI_Errhandler_set ; the
43 predefined error handler MPI_ERRORS_RETURN may be used to cause error
44 values to be returned (in C and Fortran; this error handler is less
45 useful in with the C++ MPI bindings. The predefined error handler
46 MPI::ERRORS_THROW_EXCEPTIONS should be used in C++ if the error value
47 needs to be recovered). Note that MPI does not guarantee that an MPI
48 program can continue past an error.
49 All MPI routines (except MPI_Wtime and MPI_Wtick ) return an error
51 value; C routines as the value of the function and Fortran routines in
52 the last argument. The C++ bindings for MPI do not return error val‐
53 ues; instead, error values are communicated by throwing exceptions of
54 type MPI::Exception (but not by default). Exceptions are only thrown
55 if the error value is not MPI::SUCCESS .
56 Note that if the MPI::ERRORS_RETURN handler is set in C++, while MPI
59 functions will return upon an error, there will be no way to recover
60 what the actual error value was.
61 MPI_SUCCESS
62 - No error; MPI routine completed successfully.
63 MPI_ERR_COMM
64 - Invalid communicator. A common error is to use a null commu‐
65 nicator in a call (not even allowed in MPI_Comm_rank ).
66 MPI_ERR_OTHER
67 - Other error; the error code associated with this error indi‐
68 cates an attempt to use an invalue keyval.
69 MPI_ERR_ARG
70 - Invalid argument. Some argument is invalid and is not identi‐
71 fied by a specific error class. This is typically a NULL
72 pointer or other such error.
73
76 MPI_Comm_create_keyval(3), MPI_Comm_free_keyval(3),
77 MPI_Comm_set_attr(3), MPI_Comm_delete_attr(3)
78
81 For more information, please see the official MPI Forum web site, which
82 contains the text of both the MPI-1 and MPI-2 standards. These docu‐
83 ments contain detailed information about each MPI function (most of
84 which is not duplicated in these man pages).
85 http://www.mpi-forum.org/
87
89 cgetattr.c
90LAM/MPI 7.1.2 2/23/2006 MPI_Comm_get_attr(3)