- •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
|
268 |
CHAPTER 7. |
PROCESS TOPOLOGIES |
1 |
MPI_CART_MAP(comm, ndims, |
dims, periods, |
newrank), then calling |
2MPI_COMM_SPLIT(comm, color, key, comm_cart), with color = 0 if newrank 6=
3
4
5
6
7
8
MPI_UNDEFINED, color = MPI_UNDEFINED otherwise, and key = newrank.
The function MPI_CART_SUB(comm, remain_dims, comm_new) can be implemented by a call to MPI_COMM_SPLIT(comm, color, key, comm_new), using a single number encoding of the lost dimensions as color and a single number encoding of the preserved dimensions as key.
9All other Cartesian topology functions can be implemented locally, using the topology
10
11
information that is cached with the communicator. (End of advice to implementors.)
12
13
14
15
16
17
18
19
20
The corresponding new function for general graph structures is as follows.
MPI_GRAPH_MAP(comm, nnodes, index, edges, newrank)
IN |
comm |
input communicator (handle) |
IN |
nnodes |
number of graph nodes (integer) |
IN |
index |
integer array specifying the graph structure, see |
|
|
MPI_GRAPH_CREATE |
21 |
IN |
edges |
integer array specifying the graph structure |
|
|
|
|
22 |
OUT |
newrank |
reordered rank of the calling process; |
23 |
|
|
MPI_UNDEFINED if the calling process does not be- |
24 |
|
|
long to graph (integer) |
25 |
|
|
|
26 |
int MPI_Graph_map(MPI_Comm comm, int nnodes, int *index, int *edges, |
||
|
|||
27 |
|
int *newrank) |
|
|
|
|
|
28 |
|
|
|
29 |
MPI_GRAPH_MAP(COMM, NNODES, INDEX, EDGES, NEWRANK, IERROR) |
||
|
|
|
|
30 |
INTEGER COMM, NNODES, INDEX(*), EDGES(*), NEWRANK, IERROR |
||
|
|
|
|
31 |
fint MPI::Graphcomm::Map(int nnodes, const int index[], const int edges[]) |
||
32 |
|||
|
|
const (binding deprecated, see Section 15.2) g |
33
34
35
36
37
38
39
Advice to implementors. The function MPI_GRAPH_CREATE(comm, nnodes, index, edges, reorder, comm_graph), with reorder = true can be implemented by calling
MPI_GRAPH_MAP(comm, nnodes, index, edges, newrank), then calling MPI_COMM_SPLIT(comm, color, key, comm_graph), with color = 0 if newrank 6=
MPI_UNDEFINED, color = MPI_UNDEFINED otherwise, and key = newrank.
40All other graph topology functions can be implemented locally, using the topology
41information that is cached with the communicator. (End of advice to implementors.)
42 |
|
|
43 |
7.6 An Application Example |
|
44 |
||
|
45Example 7.9 The example in Figure 7.1 shows how the grid de nition and inquiry func-
46tions can be used in an application program. A partial di erential equation, for instance
47the Poisson equation, is to be solved on a rectangular domain. First, the processes organize
48themselves in a two-dimensional structure. Each process then inquires about the ranks of
7.6. AN APPLICATION EXAMPLE |
269 |
its neighbors in the four directions (up, down, right, left). The numerical problem is solved by an iterative method, the details of which are hidden in the subroutine relax.
In each relaxation step each process computes new values for the solution grid function at all points owned by the process. Then the values at inter-process boundaries have to be exchanged with neighboring processes. For example, the exchange subroutine might contain a call like MPI_SEND(...,neigh_rank(1),...) to send updated values to the left-hand neighbor
(i-1,j).
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
270 |
CHAPTER 7. PROCESS TOPOLOGIES |
1
2
3
4
5
integer ndims, num_neigh logical reorder
parameter (ndims=2, num_neigh=4, reorder=.true.)
6integer comm, comm_cart, dims(ndims), neigh_def(ndims), ierr
7integer neigh_rank(num_neigh), own_position(ndims), i, j
8
9
logical periods(ndims)
real 8 u(0:101,0:101), f(0:101,0:101)
10data dims / ndims 0 /
11comm = MPI_COMM_WORLD
12C Set process grid size and periodicity
13call MPI_DIMS_CREATE(comm, ndims, dims,ierr)
14periods(1) = .TRUE.
15periods(2) = .TRUE.
16C Create a grid structure in WORLD group and inquire about own position
17call MPI_CART_CREATE (comm, ndims, dims, periods, reorder, comm_cart,ierr)
18call MPI_CART_GET (comm_cart, ndims, dims, periods, own_position,ierr)
19C Look up the ranks for the neighbors. Own process coordinates are (i,j).
20C Neighbors are (i-1,j), (i+1,j), (i,j-1), (i,j+1)
21i = own_position(1)
22j = own_position(2)
23neigh_def(1) = i-1
24neigh_def(2) = j
25call MPI_CART_RANK (comm_cart, neigh_def, neigh_rank(1),ierr)
26neigh_def(1) = i+1
27neigh_def(2) = j
28call MPI_CART_RANK (comm_cart, neigh_def, neigh_rank(2),ierr)
29neigh_def(1) = i
30neigh_def(2) = j-1
31call MPI_CART_RANK (comm_cart, neigh_def, neigh_rank(3),ierr)
32neigh_def(1) = i
33neigh_def(2) = j+1
34call MPI_CART_RANK (comm_cart, neigh_def, neigh_rank(4),ierr)
35C Initialize the grid functions and start the iteration
36call init (u, f)
37do 10 it=1,100
38call relax (u, f)
39C Exchange data with neighbor processes
40call exchange (u, comm_cart, neigh_rank, num_neigh)
41
42
43
44
45
46
47
10continue
call output (u) end
Figure 7.1: Set-up of process structure for two-dimensional parallel Poisson solver.
48