- •Contents
- •List of Figures
- •List of Tables
- •Acknowledgments
- •Introduction to MPI
- •Overview and Goals
- •Background of MPI-1.0
- •Background of MPI-1.1, MPI-1.2, and MPI-2.0
- •Background of MPI-1.3 and MPI-2.1
- •Background of MPI-2.2
- •Who Should Use This Standard?
- •What Platforms Are Targets For Implementation?
- •What Is Included In The Standard?
- •What Is Not Included In The Standard?
- •Organization of this Document
- •MPI Terms and Conventions
- •Document Notation
- •Naming Conventions
- •Semantic Terms
- •Data Types
- •Opaque Objects
- •Array Arguments
- •State
- •Named Constants
- •Choice
- •Addresses
- •Language Binding
- •Deprecated Names and Functions
- •Fortran Binding Issues
- •C Binding Issues
- •C++ Binding Issues
- •Functions and Macros
- •Processes
- •Error Handling
- •Implementation Issues
- •Independence of Basic Runtime Routines
- •Interaction with Signals
- •Examples
- •Point-to-Point Communication
- •Introduction
- •Blocking Send and Receive Operations
- •Blocking Send
- •Message Data
- •Message Envelope
- •Blocking Receive
- •Return Status
- •Passing MPI_STATUS_IGNORE for Status
- •Data Type Matching and Data Conversion
- •Type Matching Rules
- •Type MPI_CHARACTER
- •Data Conversion
- •Communication Modes
- •Semantics of Point-to-Point Communication
- •Buffer Allocation and Usage
- •Nonblocking Communication
- •Communication Request Objects
- •Communication Initiation
- •Communication Completion
- •Semantics of Nonblocking Communications
- •Multiple Completions
- •Non-destructive Test of status
- •Probe and Cancel
- •Persistent Communication Requests
- •Send-Receive
- •Null Processes
- •Datatypes
- •Derived Datatypes
- •Type Constructors with Explicit Addresses
- •Datatype Constructors
- •Subarray Datatype Constructor
- •Distributed Array Datatype Constructor
- •Address and Size Functions
- •Lower-Bound and Upper-Bound Markers
- •Extent and Bounds of Datatypes
- •True Extent of Datatypes
- •Commit and Free
- •Duplicating a Datatype
- •Use of General Datatypes in Communication
- •Correct Use of Addresses
- •Decoding a Datatype
- •Examples
- •Pack and Unpack
- •Canonical MPI_PACK and MPI_UNPACK
- •Collective Communication
- •Introduction and Overview
- •Communicator Argument
- •Applying Collective Operations to Intercommunicators
- •Barrier Synchronization
- •Broadcast
- •Example using MPI_BCAST
- •Gather
- •Examples using MPI_GATHER, MPI_GATHERV
- •Scatter
- •Examples using MPI_SCATTER, MPI_SCATTERV
- •Example using MPI_ALLGATHER
- •All-to-All Scatter/Gather
- •Global Reduction Operations
- •Reduce
- •Signed Characters and Reductions
- •MINLOC and MAXLOC
- •All-Reduce
- •Process-local reduction
- •Reduce-Scatter
- •MPI_REDUCE_SCATTER_BLOCK
- •MPI_REDUCE_SCATTER
- •Scan
- •Inclusive Scan
- •Exclusive Scan
- •Example using MPI_SCAN
- •Correctness
- •Introduction
- •Features Needed to Support Libraries
- •MPI's Support for Libraries
- •Basic Concepts
- •Groups
- •Contexts
- •Intra-Communicators
- •Group Management
- •Group Accessors
- •Group Constructors
- •Group Destructors
- •Communicator Management
- •Communicator Accessors
- •Communicator Constructors
- •Communicator Destructors
- •Motivating Examples
- •Current Practice #1
- •Current Practice #2
- •(Approximate) Current Practice #3
- •Example #4
- •Library Example #1
- •Library Example #2
- •Inter-Communication
- •Inter-communicator Accessors
- •Inter-communicator Operations
- •Inter-Communication Examples
- •Caching
- •Functionality
- •Communicators
- •Windows
- •Datatypes
- •Error Class for Invalid Keyval
- •Attributes Example
- •Naming Objects
- •Formalizing the Loosely Synchronous Model
- •Basic Statements
- •Models of Execution
- •Static communicator allocation
- •Dynamic communicator allocation
- •The General case
- •Process Topologies
- •Introduction
- •Virtual Topologies
- •Embedding in MPI
- •Overview of the Functions
- •Topology Constructors
- •Cartesian Constructor
- •Cartesian Convenience Function: MPI_DIMS_CREATE
- •General (Graph) Constructor
- •Distributed (Graph) Constructor
- •Topology Inquiry Functions
- •Cartesian Shift Coordinates
- •Partitioning of Cartesian structures
- •Low-Level Topology Functions
- •An Application Example
- •MPI Environmental Management
- •Implementation Information
- •Version Inquiries
- •Environmental Inquiries
- •Tag Values
- •Host Rank
- •IO Rank
- •Clock Synchronization
- •Memory Allocation
- •Error Handling
- •Error Handlers for Communicators
- •Error Handlers for Windows
- •Error Handlers for Files
- •Freeing Errorhandlers and Retrieving Error Strings
- •Error Codes and Classes
- •Error Classes, Error Codes, and Error Handlers
- •Timers and Synchronization
- •Startup
- •Allowing User Functions at Process Termination
- •Determining Whether MPI Has Finished
- •Portable MPI Process Startup
- •The Info Object
- •Process Creation and Management
- •Introduction
- •The Dynamic Process Model
- •Starting Processes
- •The Runtime Environment
- •Process Manager Interface
- •Processes in MPI
- •Starting Processes and Establishing Communication
- •Reserved Keys
- •Spawn Example
- •Manager-worker Example, Using MPI_COMM_SPAWN.
- •Establishing Communication
- •Names, Addresses, Ports, and All That
- •Server Routines
- •Client Routines
- •Name Publishing
- •Reserved Key Values
- •Client/Server Examples
- •Ocean/Atmosphere - Relies on Name Publishing
- •Simple Client-Server Example.
- •Other Functionality
- •Universe Size
- •Singleton MPI_INIT
- •MPI_APPNUM
- •Releasing Connections
- •Another Way to Establish MPI Communication
- •One-Sided Communications
- •Introduction
- •Initialization
- •Window Creation
- •Window Attributes
- •Communication Calls
- •Examples
- •Accumulate Functions
- •Synchronization Calls
- •Fence
- •General Active Target Synchronization
- •Lock
- •Assertions
- •Examples
- •Error Handling
- •Error Handlers
- •Error Classes
- •Semantics and Correctness
- •Atomicity
- •Progress
- •Registers and Compiler Optimizations
- •External Interfaces
- •Introduction
- •Generalized Requests
- •Examples
- •Associating Information with Status
- •MPI and Threads
- •General
- •Initialization
- •Introduction
- •File Manipulation
- •Opening a File
- •Closing a File
- •Deleting a File
- •Resizing a File
- •Preallocating Space for a File
- •Querying the Size of a File
- •Querying File Parameters
- •File Info
- •Reserved File Hints
- •File Views
- •Data Access
- •Data Access Routines
- •Positioning
- •Synchronism
- •Coordination
- •Data Access Conventions
- •Data Access with Individual File Pointers
- •Data Access with Shared File Pointers
- •Noncollective Operations
- •Collective Operations
- •Seek
- •Split Collective Data Access Routines
- •File Interoperability
- •Datatypes for File Interoperability
- •Extent Callback
- •Datarep Conversion Functions
- •Matching Data Representations
- •Consistency and Semantics
- •File Consistency
- •Random Access vs. Sequential Files
- •Progress
- •Collective File Operations
- •Type Matching
- •Logical vs. Physical File Layout
- •File Size
- •Examples
- •Asynchronous I/O
- •I/O Error Handling
- •I/O Error Classes
- •Examples
- •Subarray Filetype Constructor
- •Requirements
- •Discussion
- •Logic of the Design
- •Examples
- •MPI Library Implementation
- •Systems with Weak Symbols
- •Systems Without Weak Symbols
- •Complications
- •Multiple Counting
- •Linker Oddities
- •Multiple Levels of Interception
- •Deprecated Functions
- •Deprecated since MPI-2.0
- •Deprecated since MPI-2.2
- •Language Bindings
- •Overview
- •Design
- •C++ Classes for MPI
- •Class Member Functions for MPI
- •Semantics
- •C++ Datatypes
- •Communicators
- •Exceptions
- •Mixed-Language Operability
- •Problems With Fortran Bindings for MPI
- •Problems Due to Strong Typing
- •Problems Due to Data Copying and Sequence Association
- •Special Constants
- •Fortran 90 Derived Types
- •A Problem with Register Optimization
- •Basic Fortran Support
- •Extended Fortran Support
- •The mpi Module
- •No Type Mismatch Problems for Subroutines with Choice Arguments
- •Additional Support for Fortran Numeric Intrinsic Types
- •Language Interoperability
- •Introduction
- •Assumptions
- •Initialization
- •Transfer of Handles
- •Status
- •MPI Opaque Objects
- •Datatypes
- •Callback Functions
- •Error Handlers
- •Reduce Operations
- •Addresses
- •Attributes
- •Extra State
- •Constants
- •Interlanguage Communication
- •Language Bindings Summary
- •Groups, Contexts, Communicators, and Caching Fortran Bindings
- •External Interfaces C++ Bindings
- •Change-Log
- •Bibliography
- •Examples Index
- •MPI Declarations Index
- •MPI Function Index
1
2
230 CHAPTER 6. GROUPS, CONTEXTS, COMMUNICATORS, AND CACHING
LOGICAL FLAG
3fbool MPI::Comm::Get_attr(int comm_keyval, void* attribute_val) const
4 |
(binding deprecated, see Section 15.2) g |
5Retrieves attribute value by key. The call is erroneous if there is no key with value
6keyval. On the other hand, the call is correct if the key value exists, but no attribute is
7attached on comm for that key; in such case, the call returns flag = false. In particular
8
9
MPI_KEYVAL_INVALID is an erroneous key value.
10Advice to users. The call to MPI_Comm_set_attr passes in attribute_val the value of
11the attribute; the call to MPI_Comm_get_attr passes in attribute_val the address of the
12location where the attribute value is to be returned. Thus, if the attribute value itself is
13a pointer of type void*, then the actual attribute_val parameter to MPI_Comm_set_attr
14will be of type void* and the actual attribute_val parameter to MPI_Comm_get_attr
15will be of type void**. (End of advice to users.)
16
Rationale. The use of a formal parameter attribute_val or type void* (rather than
17
void**) avoids the messy type casting that would be needed if the attribute value is
18
declared with a type other than void*. (End of rationale.)
19
20
This function replaces MPI_ATTR_GET, whose use is deprecated. The C binding is
21
identical. The Fortran binding di ers in that attribute_val is an address-sized integer.
22
23
24 |
MPI_COMM_DELETE_ATTR(comm, comm_keyval) |
|
25
26
27
28
29
INOUT |
comm |
communicator from which the attribute is deleted (han- |
|
|
dle) |
IN |
comm_keyval |
key value (integer) |
30 int MPI_Comm_delete_attr(MPI_Comm comm, int comm_keyval)
31
MPI_COMM_DELETE_ATTR(COMM, COMM_KEYVAL, IERROR)
32
INTEGER COMM, COMM_KEYVAL, IERROR
33
34 |
fvoid MPI::Comm::Delete_attr(int comm_keyval) (binding deprecated, see |
|
35 |
Section 15.2) g |
|
|
||
36 |
Delete attribute from cache by key. This function invokes the attribute delete function |
|
37 |
||
comm_delete_attr_fn speci ed when the keyval was created. The call will fail if the |
||
38 |
||
comm_delete_attr_fn function returns an error code other than MPI_SUCCESS. |
||
39 |
||
Whenever a communicator is replicated using the function MPI_COMM_DUP, all call- |
||
40 |
||
back copy functions for attributes that are currently set are invoked (in arbitrary order). |
||
41 |
||
Whenever a communicator is deleted using the function MPI_COMM_FREE all callback |
||
42 |
||
delete functions for attributes that are currently set are invoked. |
||
43 |
||
This function is the same as MPI_ATTR_DELETE but is needed to match the new |
||
44 |
||
communicator speci c functions. The use of MPI_ATTR_DELETE is deprecated. |
||
45 |
||
|
||
46 |
|
47
48
6.7.3 Windows
The new functions for caching on windows are:
6.7. CACHING |
231 |
MPI_WIN_CREATE_KEYVAL(win_copy_attr_fn, win_delete_attr_fn, win_keyval, extra_state)
IN |
win_copy_attr_fn |
copy callback function for win_keyval (function) |
IN |
win_delete_attr_fn |
delete callback function for win_keyval (function) |
OUT |
win_keyval |
key value for future access (integer) |
IN |
extra_state |
extra state for callback functions |
int MPI_Win_create_keyval(MPI_Win_copy_attr_function *win_copy_attr_fn, MPI_Win_delete_attr_function *win_delete_attr_fn,
int *win_keyval, void *extra_state)
MPI_WIN_CREATE_KEYVAL(WIN_COPY_ATTR_FN, WIN_DELETE_ATTR_FN, WIN_KEYVAL, EXTRA_STATE, IERROR)
EXTERNAL WIN_COPY_ATTR_FN, WIN_DELETE_ATTR_FN
INTEGER WIN_KEYVAL, IERROR
INTEGER(KIND=MPI_ADDRESS_KIND) EXTRA_STATE
fstatic int MPI::Win::Create_keyval(MPI::Win::Copy_attr_function* win_copy_attr_fn,
MPI::Win::Delete_attr_function* win_delete_attr_fn, void* extra_state) (binding deprecated, see Section 15.2) g
The argument win_copy_attr_fn may be speci ed as MPI_WIN_NULL_COPY_FN or
MPI_WIN_DUP_FN from either C, C++, or Fortran. MPI_WIN_NULL_COPY_FN is a function that does nothing other than returning ag = 0 and MPI_SUCCESS. MPI_WIN_DUP_FN is a simple-minded copy function that sets ag = 1, returns the value of attribute_val_in in attribute_val_out, and returns MPI_SUCCESS.
The argument win_delete_attr_fn may be speci ed as MPI_WIN_NULL_DELETE_FN from either C, C++, or Fortran. MPI_WIN_NULL_DELETE_FN is a function that does nothing, other than returning MPI_SUCCESS.
The C callback functions are:
typedef int MPI_Win_copy_attr_function(MPI_Win oldwin, int win_keyval, void *extra_state, void *attribute_val_in,
void *attribute_val_out, int *flag);
and
typedef int MPI_Win_delete_attr_function(MPI_Win win, int win_keyval, void *attribute_val, void *extra_state);
The Fortran callback functions are:
SUBROUTINE WIN_COPY_ATTR_FN(OLDWIN, WIN_KEYVAL, EXTRA_STATE, ATTRIBUTE_VAL_IN, ATTRIBUTE_VAL_OUT, FLAG, IERROR)
INTEGER OLDWIN, WIN_KEYVAL, IERROR INTEGER(KIND=MPI_ADDRESS_KIND) EXTRA_STATE, ATTRIBUTE_VAL_IN,
ATTRIBUTE_VAL_OUT
LOGICAL FLAG
and
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
232 CHAPTER 6. GROUPS, CONTEXTS, COMMUNICATORS, AND CACHING
1SUBROUTINE WIN_DELETE_ATTR_FN(WIN, WIN_KEYVAL, ATTRIBUTE_VAL, EXTRA_STATE,
2
3
IERROR)
INTEGER WIN, WIN_KEYVAL, IERROR
4INTEGER(KIND=MPI_ADDRESS_KIND) ATTRIBUTE_VAL, EXTRA_STATE
5
6The C++ callbacks are:
7ftypedef int MPI::Win::Copy_attr_function(const MPI::Win& oldwin,
8
9
10
int win_keyval, void* extra_state, void* attribute_val_in, void* attribute_val_out, bool& flag); (binding deprecated, see Section 15.2) g
11and
12ftypedef int MPI::Win::Delete_attr_function(MPI::Win& win, int win_keyval,
13
14
15
void* attribute_val, void* extra_state); (binding deprecated, see Section 15.2) g
16If an attribute copy function or attribute delete function returns other than
17MPI_SUCCESS, then the call that caused it to be invoked (for example, MPI_WIN_FREE), is
18erroneous.
19
20
21
22
23
MPI_WIN_FREE_KEYVAL(win_keyval)
INOUT win_keyval |
key value (integer) |
24 int MPI_Win_free_keyval(int *win_keyval)
25
MPI_WIN_FREE_KEYVAL(WIN_KEYVAL, IERROR)
26
INTEGER WIN_KEYVAL, IERROR
27
28 |
fstatic void MPI::Win::Free_keyval(int& win_keyval) (binding deprecated, see |
29 |
Section 15.2) g |
|
30
31
32
33
34
35
36
37
38
39
MPI_WIN_SET_ATTR(win, win_keyval, attribute_val)
INOUT |
win |
window to which attribute will be attached (handle) |
IN |
win_keyval |
key value (integer) |
IN |
attribute_val |
attribute value |
int MPI_Win_set_attr(MPI_Win win, int win_keyval, void *attribute_val)
40MPI_WIN_SET_ATTR(WIN, WIN_KEYVAL, ATTRIBUTE_VAL, IERROR)
41INTEGER WIN, WIN_KEYVAL, IERROR
42INTEGER(KIND=MPI_ADDRESS_KIND) ATTRIBUTE_VAL
43
fvoid MPI::Win::Set_attr(int win_keyval, const void* attribute_val) (binding
44
deprecated, see Section 15.2) g
45
46
47
48
6.7. CACHING |
233 |
MPI_WIN_GET_ATTR(win, win_keyval, attribute_val, ag)
IN |
win |
window to which the attribute is attached (handle) |
IN |
win_keyval |
key value (integer) |
OUT |
attribute_val |
attribute value, unless ag = false |
OUT |
ag |
false if no attribute is associated with the key (logical) |
1
2
3
4
5
6
7
8
int MPI_Win_get_attr(MPI_Win win, int win_keyval, void *attribute_val, int *flag)
MPI_WIN_GET_ATTR(WIN, WIN_KEYVAL, ATTRIBUTE_VAL, FLAG, IERROR) INTEGER WIN, WIN_KEYVAL, IERROR INTEGER(KIND=MPI_ADDRESS_KIND) ATTRIBUTE_VAL
LOGICAL FLAG
9
10
11
12
13
14
15
fbool MPI::Win::Get_attr(int win_keyval, void* attribute_val) const (binding deprecated, see Section 15.2) g
MPI_WIN_DELETE_ATTR(win, win_keyval)
INOUT |
win |
window from which the attribute is deleted (handle) |
16
17
18
19
20
21
22
IN |
win_keyval |
key value (integer) |
int MPI_Win_delete_attr(MPI_Win win, int win_keyval)
MPI_WIN_DELETE_ATTR(WIN, WIN_KEYVAL, IERROR)
INTEGER WIN, WIN_KEYVAL, IERROR
fvoid MPI::Win::Delete_attr(int win_keyval) (binding deprecated, see Section 15.2) g
23
24
25
26
27
28
29
30
31
32
6.7.4 Datatypes
The new functions for caching on datatypes are:
33
34
35
36
MPI_TYPE_CREATE_KEYVAL(type_copy_attr_fn, type_delete_attr_fn, type_keyval, extra_state) 37
|
|
|
38 |
|
IN |
type_copy_attr_fn |
copy callback function for type_keyval (function) |
39 |
|
|
||||
IN |
type_delete_attr_fn |
delete callback function for type_keyval (function) |
40 |
|
41 |
||||
|
|
|
||
OUT |
type_keyval |
key value for future access (integer) |
42 |
|
IN |
extra_state |
extra state for callback functions |
43 |
|
|
||||
|
|
|
44 |
45
int MPI_Type_create_keyval(MPI_Type_copy_attr_function *type_copy_attr_fn,
46
MPI_Type_delete_attr_function *type_delete_attr_fn,
47
int *type_keyval, void *extra_state)
48
234 CHAPTER 6. GROUPS, CONTEXTS, COMMUNICATORS, AND CACHING
1MPI_TYPE_CREATE_KEYVAL(TYPE_COPY_ATTR_FN, TYPE_DELETE_ATTR_FN, TYPE_KEYVAL,
2
3
4
5
6
EXTRA_STATE, IERROR)
EXTERNAL TYPE_COPY_ATTR_FN, TYPE_DELETE_ATTR_FN
INTEGER TYPE_KEYVAL, IERROR
INTEGER(KIND=MPI_ADDRESS_KIND) EXTRA_STATE
7fstatic int MPI::Datatype::Create_keyval(MPI::Datatype::Copy_attr_function*
8
9
10
type_copy_attr_fn, MPI::Datatype::Delete_attr_function* type_delete_attr_fn, void* extra_state) (binding deprecated, see Section 15.2) g
11The argument type_copy_attr_fn may be speci ed as MPI_TYPE_NULL_COPY_FN or
12MPI_TYPE_DUP_FN from either C, C++, or Fortran. MPI_TYPE_NULL_COPY_FN is a
13function that does nothing other than returning ag = 0 and MPI_SUCCESS.
14MPI_TYPE_DUP_FN is a simple-minded copy function that sets ag = 1, returns the value
15of attribute_val_in in attribute_val_out, and returns MPI_SUCCESS.
16The argument type_delete_attr_fn may be speci ed as MPI_TYPE_NULL_DELETE_FN
17from either C, C++, or Fortran. MPI_TYPE_NULL_DELETE_FN is a function that does
18nothing, other than returning MPI_SUCCESS.
19The C callback functions are:
20typedef int MPI_Type_copy_attr_function(MPI_Datatype oldtype,
21
22
23
int type_keyval, void *extra_state, void *attribute_val_in,
void *attribute_val_out, int *flag);
24and
25typedef int MPI_Type_delete_attr_function(MPI_Datatype type,
26 |
int type_keyval, void *attribute_val, void *extra_state); |
27The Fortran callback functions are:
28SUBROUTINE TYPE_COPY_ATTR_FN(OLDTYPE, TYPE_KEYVAL, EXTRA_STATE,
29
30
31
32
ATTRIBUTE_VAL_IN, ATTRIBUTE_VAL_OUT, FLAG, IERROR)
INTEGER OLDTYPE, TYPE_KEYVAL, IERROR
INTEGER(KIND=MPI_ADDRESS_KIND) EXTRA_STATE,
ATTRIBUTE_VAL_IN, ATTRIBUTE_VAL_OUT
33
34
LOGICAL FLAG
35and
36SUBROUTINE TYPE_DELETE_ATTR_FN(TYPE, TYPE_KEYVAL, ATTRIBUTE_VAL,
37 |
EXTRA_STATE, IERROR) |
38INTEGER TYPE, TYPE_KEYVAL, IERROR
39INTEGER(KIND=MPI_ADDRESS_KIND) ATTRIBUTE_VAL, EXTRA_STATE
40
The C++ callbacks are:
41
ftypedef int
42
43
44
45
46
47
MPI::Datatype::Copy_attr_function(const MPI::Datatype& oldtype, int type_keyval, void* extra_state,
const void* attribute_val_in, void* attribute_val_out, bool& flag); (binding deprecated, see Section 15.2) g
and
48
6.7. CACHING |
235 |
ftypedef int MPI::Datatype::Delete_attr_function(MPI::Datatype& type, int type_keyval, void* attribute_val, void* extra_state);
(binding deprecated, see Section 15.2) g
If an attribute copy function or attribute delete function returns other than MPI_SUCCESS, then the call that caused it to be invoked (for example, MPI_TYPE_FREE), is erroneous.
MPI_TYPE_FREE_KEYVAL(type_keyval)
INOUT type_keyval key value (integer)
int MPI_Type_free_keyval(int *type_keyval) MPI_TYPE_FREE_KEYVAL(TYPE_KEYVAL, IERROR)
INTEGER TYPE_KEYVAL, IERROR
fstatic void MPI::Datatype::Free_keyval(int& type_keyval) (binding deprecated, see Section 15.2) g
MPI_TYPE_SET_ATTR(type, type_keyval, attribute_val)
INOUT |
type |
datatype to which attribute will be attached (handle) |
IN |
type_keyval |
key value (integer) |
IN |
attribute_val |
attribute value |
int MPI_Type_set_attr(MPI_Datatype type, int type_keyval, void *attribute_val)
MPI_TYPE_SET_ATTR(TYPE, TYPE_KEYVAL, ATTRIBUTE_VAL, IERROR) INTEGER TYPE, TYPE_KEYVAL, IERROR INTEGER(KIND=MPI_ADDRESS_KIND) ATTRIBUTE_VAL
fvoid MPI::Datatype::Set_attr(int type_keyval, const void* attribute_val)
(binding deprecated, see Section 15.2) g
MPI_TYPE_GET_ATTR(type, type_keyval, attribute_val, ag)
IN |
type |
datatype to which the attribute is attached (handle) |
IN |
type_keyval |
key value (integer) |
OUT |
attribute_val |
attribute value, unless ag = false |
OUT |
ag |
false if no attribute is associated with the key (logical) |
int MPI_Type_get_attr(MPI_Datatype type, int type_keyval, void *attribute_val, int *flag)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
MPI_TYPE_GET_ATTR(TYPE, TYPE_KEYVAL, ATTRIBUTE_VAL, FLAG, IERROR) |
48 |