MPI - Montefiore Institutemontefiore.ulg.ac.be/~geuzaine/INFO0939/MPI.pdf · Tips & Tricks • Questions: Which compilers are available ? Where ? ... ‣ buffer (start of the memory

MPIMESSAGE PASSING INTERFACE

David COLIGNON

CÉCI - Consortium des Équipements de Calcul Intensifhttp://hpc.montefiore.ulg.ac.be

http://hpc.montefiore.ulg.ac.be

http://hpc.montefiore.ulg.ac.be

2

Outline• Introduction

• From serial source code to parallel execution

• MPI functions I

‣ Global Environment

‣ Point-to-Point Communication

• Exercice

• MPI functions II

‣ Collective Communication

‣ Global Reduction Operations

‣ Communication Modes

• References

!"#$%&'$())* +

,-./0-12/34$!3560#

! !"#$%&'(#)**('%$"*%+,*%(-.%&'+/",)%0)0('1

! !2&3+#+,%#(004.+#",+(.

! !2&3+#+,%*1.#$'(.+5",+(.

! 6+77+#43,%,(%&'(8'"0%94,%.(:7)-%$+;;).%*+;)<)77)#,*

=.,)'#(..)#,

>?@

A)0('1

>?@

A)0('1

>?@

A)0('1

>?@

A)0('1

>?@

A)0('1

>?@

A)0('1

3

Introduction: Target

Each "processor" has its own memoryor separate address space

4

• What is parallel programming ?

• What are the (your) goals ?

‣

‣

Introduction: Goal

5

• What is parallel programming ?

• What are the (your) goals ?

‣ Decrase the total execution time

‣ Solve bigger problems

• Solution: Partition the work so that all processors are busy and none remain idle

• Partitioning a problem into workable subproblems: OK

Introduction: Goal

6

Introduction: the MPI solution

• How to partition efficiently my problem to solve it in // ?

• How can we get processors to work in // ?

• Solution: by exchanging messages

• To achieve a common parallel task, data are shared by sending/receiving "messages"

• Message Passing Interface: most widely used standard for parallel programming

7

• It's not a new programming language: it's a library of normalized functions for inter-process communication (can be called from Fortran, C, C++, ...)

‣ Every processor runs the same executable

‣ Processes communicates with each other through the "infrastructure" provided by MPI.

• At first, no need to know the details of the implementation. You just need to know how to take advantage of it


8

• Carefully designed to permit maximum performance on a wide variety of systems

• Emphasis on Portability and Efficiency

• Hide many details but expose many others to the programmer

• Sometimes called the "assembly language" of parallel computing


9

• each node/cpu/processor/core runs the same executable and works on its local data

• Data are shared by sending/receiving "messages"

• MPI functions

‣ Global management of the communications

‣ Point-to-Point communication

‣ Global communication


10

! serial

program helloser

print * , "Hello World !"

end

! f90 hello.cpp

! ./a.out

! parallel

program hellopar

include 'mpif.h'integer err

call MPI_INIT(err)

print * , "Hello World !"

call MPI_FINALIZE(err)

end

! mpif90 hello_mpi.cpp

! mpirun -np 3 ./a.out

From serial source code to parallel execution

11

Tips & Tricks• Questions: Which compilers are available ? Where ?

Is MPI installed ? Where ? Which version should I use ?

• Answers: R T F M !

echo $PATH

mpi “+ TAB”

module available ; module add...

mpif90 -show

gfortran -v ; ifc -V

which mpirun ; type mpirun

12

MPI : Overview• All MPI function begins with MPI_

• All MPI function returns an error code( = MPI_SUCCES if OK )

• Each processor runs exactly the same executable:mpirun -np 4 prog.exe < input.txt

mpirun -np 4 /path_to/prog.exe < /path_to/input.txt

13

MPI: Global Environment

• A minimal MPI program ( like hellopar.f90 ) contains:

‣ Include ‘mpif.h’( mpi.h in C/C++ )

‣ call MPI_INIT(err) before any call to a MPI function, in order to initialize the environment

‣ call MPI_FINALIZE(err) after the last call to a MPI function

14


• A Communicator is a pool of processes that can communicate together

• MPI_COMM_WORLD is the default communicator which contains all the active processes ( mpirun -np 8 -machinefile mach.txt ./a.out )

• In a communicator, each process get identified by his rank , from 0 to ( np - 1)

15


• A process can get back the total number of processes in a communicator with:

integer nbproc, err

call MPI_COMM_SIZE( MPI_COMM_WORLD, nbproc, err )

• A process can know his rank inside the communicator with:

integer myrank, err

call MPI_COMM_RANK( MPI_COMM_WORLD, myrank, err )

16

program hellopar2

include 'mpif.h'

integer err, nbproc, myrank

call MPI_INIT(err)

call MPI_COMM_RANK( MPI_COMM_WORLD, myrank, ierr )

call MPI_COMM_SIZE( MPI_COMM_WORLD, nbproc, ierr )

print *, "Hello world ! from proc", myrank, &

" of " , nbproc


end program hellopar2

Hello World! 2.0

17

Point-to-Point Communication

• Bilateral communication between two processes (emitter and receiver), identified by their rank in their common communicator

• SEND and RECEIVE are mandatory

• Message = Envelope + Body

• Envelope:

‣ rank of the source process

‣ rank of the destination process

‣ tag (integer) to classify the messages

‣ communicator

18

Point-to-Point Communication• Message = Envelope + Body

• Body:‣ buffer (start of the memory area where

the data are located)

‣ count ( number of elements)

‣ datatype

3 – Communications point a point : types de base 23

3.2 – Types de donnees de base

Tab. 1 – Principaux types de donnees de base (Fortran)

Type MPI Type Fortran

MPI INTEGER INTEGER

MPI REAL REAL

MPI DOUBLE PRECISION DOUBLE PRECISION

MPI COMPLEX COMPLEX

MPI LOGICAL LOGICAL

MPI CHARACTER CHARACTER

MPI PACKED Types heterogenes

INSTITUT DU DEVELOPPEMENT

ET DES RESSOURCES

EN INFORMATIQUE SCIENTIFIQUE

MPI-1 – Version 2.18 – Novembre 2006

J. Chergui, I. Dupays, D. Girou, S. Requena, P. Wautelet

19

MPI_SEND & MPI_RECV

• MPI_SEND( BUF, COUNT, DTYPE, DEST, TAG, COMM, ERR )

• MPI_RECV( BUF, COUNT, DTYPE, SOURCE, TAG, COMM, STATUS, ERR)

‣ envelope ( SOURCE, TAG, COMM ) determines which message can be received

‣ “wild cards” MPI_ANY_SOURCE & MPI_ANY_TAG can be used

‣ STATUS contains SOURCE & TAG (if wild cards were used), and number of received data

20

MPI_SEND & MPI_RECV


• In C, status is a structure ( MPI_Status status ) that contains three fields named MPI_SOURCE , MPI_TAG , and MPI_ERRORThe structure may contain additional fields. status.MPI_SOURCE , status.MPI_TAG and status.MPI_ERROR contain the source, tag, and error code of the received message.

• In Fortran, status is an array of INTEGERs of size MPI_STATUS_SIZE ( INTEGER :: status(MPI_STATUS_SIZE) ). The constants MPI_SOURCE , MPI_TAG and MPI_ERROR are the indices of the entries that store the source, tag and error fields. Thus, status(MPI_SOURCE) , status(MPI_TAG), and status(MPI_ERROR) contain the source, tag and error code of the received message.

21

MPI_SEND & MPI_RECV

• MPI_SEND( BUF, COUNT, DTYPE, DEST, TAG, COMM, ERR )


‣ error if received message longer than expected( by COUNT and DTYPE )

‣ DTYPE of MPI_SEND and MPI_RECV must match

22

MPI_SEND & MPI_RECV

• MPI_SEND and MPI_RECV are blocking !operation must be completed before jump tonext instruction

•Asynchronous communication: possible delay between Send and Receive, sent data could be buffered. Even if Send is completed, it doesn’t mean that message has already been received

•Be cautious with Deadlocks: two processes waiting for a message that never come

23

MPI_SEND & MPI_RECV : Deadlocks! this code hangs !

if( myrank.eq.0 ) then

call MPI_RECV( b, 100, MPI_REAL, &

1, 39, MPI_COMM_WORLD, status, err)

call MPI_SEND( a, 100, MPI_REAL, &

1, 17, MPI_COMM_WORLD, err)

else if ( myrank.eq.1 ) then


0, 17, MPI_COMM_WORLD, status, err )



endif

24

MPI_SEND & MPI_RECV : Deadlocks! this code hangs !

if( myrank.eq.0 ) then


1, 39, MPI_COMM_WORLD, status, err)


1, 17, MPI_COMM_WORLD, ierr)

else if ( myrank.eq.1 ) then




0, 17, MPI_COMM_WORLD, status, err )

endif

25

Exercice: Sum of the first N Integers! serial solution

program sumserial

integer :: N = 1000, sum = 0, i

do i = 1 , N

sum = sum + i

end do

print *, "The sum from 1 to", N , "is:", sum

end program sumserial

26

Sum of the first N Integers: Parallel

• How to Partition ?

• Magic Formula:

startval = N * myrank / nbproc + 1

endval = N * (myrank+1) / nbproc

• ! Caution ! Integer division

• Process of rank 0 receive partial sums and add

27

Exercice: Sum of the first N Integers! SOME HINTS

implicit none

include 'mpif.h'

integer :: err, myrank, nbproc, status(MPI_STATUS_SIZE)

call MPI_INIT(err)

call MPI_COMM_RANK( MPI_COMM_WORLD , myrank, err )

call MPI_COMM_SIZE( MPI_COMM_WORLD , nbproc, err )

call MPI_SEND( partsum, 1, MPI_INTEGER, &

0, 23, MPI_COMM_WORLD, err )

call MPI_RECV( tmpsum, 1, MPI_INTEGER, &

i, 23, MPI_COMM_WORLD, status, err )


28

Exercice: Sum of the first N Integers! parallel solutionprogram sumpar1 implicit none include 'mpif.h' integer :: err, myrank, nbproc, status(MPI_STATUS_SIZE) integer :: startval, endval, N=1000, i, partsum, tmpsum call MPI_INIT(ierr) call MPI_COMM_RANK( MPI_COMM_WORLD , myrank, err ) call MPI_COMM_SIZE( MPI_COMM_WORLD , nbproc , err ) startval = N * myrank / nbproc + 1 endval = N * (myrank+1) / nbproc partsum = 0 ; tmpsum = 0 do i = startval, endval partsum = partsum + i end do print * , "partial sum from", startval, "to", endval, & "on proc", myrank, "equals", partsum

29

Exercice: Sum of the first N Integers if( myrank.ne.0 ) then call MPI_SEND( partsum, 1, MPI_INTEGER, & 0, 23,MPI_COMM_WORLD, err ) else do i = 1 , nproc - 1 call MPI_RECV( tmpsum, 1, MPI_INTEGER, & i, 23, MPI_COMM_WORLD, status, err) partsum = partsum + tmpsum enddo endif if( myrank.eq. 0 ) then print *, "The sum from 1 to", N, "is:", partsum endif call MPI_FINALIZE(err)end program sumpar1

30


Edinburgh Parallel Computing Centre 11

If a program breaks these rules, unpredictable behaviour can result: programs mayrun successfully on one implementation of MPI but not on others, or may run success-fully on some occasions and “hang” on other occasions in a non-deterministic way.

The standard send has the following form

MPI_SEND (buf, count, datatype, dest, tag, comm)

where

• buf is the address of the data to be sent.

• count is the number of elements of the MPI datatype which buf contains.

• datatype is the MPI datatype.

• dest is the destination process for the message. This is specified by the rank ofthe destination process within the group associated with the communicatorcomm.

• tag is a marker used by the sender to distinguish between different types ofmessages. Tags are used by the programmer to distinguish between differentsorts of message.

• comm is the communicator shared by the sending and receiving processes. Onlyprocesses which have the same communicator can communicate.

• IERROR contains the return value of the Fortran version of the synchronoussend.

Completion of a send means by definition that the send buffer can safely be re-used i.e.the data has been sent.

3.2.2 Synchronous Send

If the sending process needs to know that the message has been received by thereceiving process, then both processes may use synchronous communication. Whatactually happens during a synchronous communication is something like this: thereceiving process sends back an acknowledgement (a procedure known as a ‘hand-shake’ between the processes) as shown in Figure 4:. This acknowledgement must bereceived by the sender before the send is considered complete.

Figure 4: In the synchronous mode the sender knows that the other one has received the mes-sage.

The MPI synchronous send routine is similar in form to the standard send. For exam-ple, in the blocking form:

MPI_SSEND (buf, count, datatype, dest, tag, comm)

0

4

2

3

51

communicator

31



shown in Figure 5:, the sending process simply throws the message out onto the com-munication network and hopes that the receiving process is waiting to catch it. If thereceiving process is ready for the message, it will be received, else the message may besilently dropped, an error may occur, etc.

Figure 5: In the ready mode a process hopes that the other process has caught the message

The idea is that by avoiding the necessity for handshaking and buffering between thesender and the receiver, performance may be improved. Use of ready mode is onlysafe if the logical control flow of the parallel program permits it. For example, see Fig-ure 6:

Figure 6: An example of safe use of ready mode. When Process 0 sends the message with tag0 it ``knows'' that the receive has already been posted because of the synchronisation inherent

in sending the message with tag 1.

Clearly ready mode is a difficult mode to debug and requires careful attention to par-allel program messaging patterns. It is only likely to be used in programs for whichperformance is critical and which are targeted mainly at platforms for which there is areal performance gain. The ready send has a similar form to the standard send:

MPI_RSEND (buf, count, datatype, dest, tag, comm)

Non-blocking ready send has no advantage over blocking ready send (see“Non-Blocking Communication” on page 19).

3.2.5 The standard blocking receive

The format of the standard blocking receive is:

MPI_RECV (buf, count, datatype, source, tag, comm, status)

where

0

4

2

3

51

communicator

Process 0

non!blocking receive from process 0 with tag 0

blocking receive froprocess 0 with tag 1

ynchronous send to rocess 1 with tag 1

ready send to process 1 with tag 0

Process 1time

received

test non!blocking receive

Writing Message Passing Parallel Programs with MPI

14 Course notes

• buf is the address where the data should be placed once received (the receivebuffer). For the communication to succeed, the receive buffer must be largeenough to hold the message without truncation — if it is not, behaviour is un-defined. The buffer may however be longer than the data received.

• count is the number of elements of a certain MPI datatype which buf can con-tain. The number of data elements actually received may be less than this.

• datatype is the MPI datatype for the message. This must match the MPI da-tatype specified in the send routine.

• source is the rank of the source of the message in the group associated with thecommunicator comm. Instead of prescribing the source, messages can be re-ceived from one of a number of sources by specifying a wildcard,MPI_ANY_SOURCE, for this argument.

• tag is used by the receiving process to prescribe that it should receive only amessage with a certain tag. Instead of prescribing the tag, the wildcardMPI_ANY_TAG can be specified for this argument.

• comm is the communicator specified by both the sending and receiving process.There is no wildcard option for this argument.

• If the receiving process has specified wildcards for both or either of source ortag, then the corresponding information from the message that was actually re-ceived may be required. This information is returned in status, and can bequeried using routines described later.

• IERROR contains the return value of the Fortran version of the standard receive.

Completion of a receive means by definition that a message arrived i.e. the data hasbeen received.

3.3 Discussion

The word “blocking” means that the routines described above only return once the com-munication has completed. This is a non-local condition i.e. it might depend on the stateof other processes. The ability to select a message by source is a powerful feature. Forexample, a source process might wish to receive messages back from worker proc-esses in strict order. Tags are another powerful feature. A tag is an integer labellingdifferent types of message, such as “initial data”, “client-server request”, “resultsfrom worker”. Note the difference between this and the programmer sending an inte-ger label of his or her own as part of the message — in the latter case, by the time thelabel is known, the message itself has already been read. The point of tags is that thereceiver can select which messages it wants to receive, on the basis of the tag.Point-to-point communications in MPI are led by the sending process “pushing” mes-sages out to other processes — a process cannot “fetch” a message, it can only receivea message if it has been sent. When a point-to-point communication call is made, it istermed posting a send or posting a receive, in analogy perhaps to a bulletin board.Because of the selection allowed in receive calls, it makes sense to talk of a sendmatching a receive. MPI can be thought of as an agency — processes post sends andreceives to MPI and MPI matches them up.

32

Outline• Introduction

• From serial source code to parallel execution

• MPI functions I

‣ Global Environment

‣ Point-to-Point Communication

• Exercice

• MPI functions II

‣ Collective Communication

‣ Global Reduction Operations

‣ Communication Modes

• References

33

Collective Communications

• Global function called within all the processes of a specified communicator

• cannot interfere with p2p communications

• All the processes must call the same sequence of global functions in the same order

• MPI_Barrier( MPI_COMM_WORLD, err )

blocks the calling process untill all others process int the communicator have called it : Synchronization Barrier

34

9.1. Gaussian Elimination 540

Process 0

databuffer databuffer

x00 x01

Process 1

Process 2

x00 x01

x00 x01

x00 x01

Figure 9.7: MPI Bcast schematic demonstrating a broadcast of two data objects from processzero to all other processes.

We now present a parallel implementation of Gaussian elimination with back substitution.As a model problem, we solve for the interpolating polynomial of the Runge function (seesection 3.1.4) by forming a Vandermonde matrix based on the Chebyshev points. Recall thatthe goal is to find the polynomial coe!cients by solving the system Ax = b where A is theVandermonde matrix and b is the function of interest evaluated at the interpolation points.

To better explain the code, we have broken the entire program into six parts, labeledpart one through part six. The six parts break down the code as follows:

1. Part 1 - MPI initialization/setup and initial memory allocations.

2. Part 2 - Generation of the matrix rows local to each process.

3. Part 3 - Gaussian elimination of the augmented matrix.

4. Part 4 - Preparation for back substitution.

5. Part 5 - Back substitution to find the solution.

6. Part 6 - Program finalization and clean-up.

For each part, we will first present the code and then present a collection of remarkselucidating the salient points within each part.

Part 1 - MPI initialization

#include <iostream.h>#include <iomanip.h>#include "SCmathlib.h"#include "SCchapter3.h"#include<mpi.h>

void ChebyVandermonde(int npts, double *A, int row);

Broadcast: MPI_BCAST

35

MPI_BCAST

Tree Implementation

• MPI_BCAST( buffer, count, datatype, root, comm)

• A broadcast has a specified root process and every process receives one copy of the message from the root.

• All processes must specify the same root (and communicator).

• The root argument is the rank of the root process.

• The buffer, count and datatype arguments are treated as in a point-to-point send on the root and as in a point-to-point receive elsewhere.

36

MPI_BCAST

37

MPI_BCAST ExamplePROGRAM broadcast

INCLUDE 'mpif.h'

INTEGER err, myrank, nbproc

REAL param

CALL MPI_INIT(err)

CALL MPI_COMM_RANK(MPI_COMM_WORLD, myrank, err)

CALL MPI_COMM_SIZE(MPI_COMM_WORLD, nbproc, err)

if( myrank.eq.(nbproc-1) ) param=23.0

call MPI_BCAST( param, 1, MPI_REAL, &

(nbproc-1), MPI_COMM_WORLD, err)

print *,'On Proc', myrank,'after bcast param=', param

CALL MPI_FINALIZE(err)

END PROGRAM broadcast


42 Course notes

MPI_BARRIER (COMM)

MPI_BARRIER blocks the calling process until all other group members have called it.

In one phase of a computation, all processes participate in writing a file. The file is tobe used as input data for the next phase of the computation. Therefore no processshould proceed to the second phase until all processes have completed phase one.

7.2 Broadcast, scatter, gather, etc.

Figure 24: Schematic illustration of broadcast/scatter/gather operations. The circles representprocesses with ranks as shown. The small boxes represent buffer space and the letters representdata items. Receive buffers are represented by the empty boxes on the ``before'' side, send buff-

ers by the full boxes.

This set of routines distributes and re-distributes data without performing any opera-tions on the data. The routines are shown schematically in Figure 24:. The full set ofroutines is as follows, classified here according to the form of the routine call.

7.2.1 MPI_BCAST

A broadcast has a specified root process and every process receives one copy of themessage from the root. All processes must specify the same root (and communicator).

MPI_BCAST (buffer, count, datatype, root, comm)

The root argument is the rank of the root process. The buffer, count anddatatype arguments are treated as in a point-to-point send on the root and as in apoint-to-point receive elsewhere.

7.2.2 MPI_SCATTER, MPI_GATHER

These routines also specify a root process and all processes must specify the same root(and communicator). The main difference from MPI_BCAST is that the send andreceive details are in general different and so must both be specified in the argumentlists. The argument lists are the same for both routines, so only MPI_SCATTER isshown here.

B B BBBB

A B C D E

A B C D E A B C D EA B C D EA B C D EA B C D E

ROOT

ROOT

A B C D E F G H I J K L M N O P Q R S T U V W X Y

A G M YB C D EF H I JK L N OP Q R S TU V W X

1 2 3 4 1 2 3 4RANK

MPI_BCAST

MPI_SCATTER

MPI_GATHER

MPI_ALLGATHER

MPI_ALL_TO_ALL

Before After

A B C D E

C D EA B

A B C D E

ROOT

C D EA B C D EA B

A B C D E F G H I J K L M N O P Q R S T U V W X Y

C D EA B C D EA B

0 0

38

39

MPI_SCATTER

40

MPI_SCATTER• MPI_SCATTER( sendbuf, sendcount, sendtype,

recvbuf, recvcount, recvtype, root, comm, err)

• Specify a root process and all processes must specify the same root (and communicator)

• The main difference from MPI_BCAST is that the send and receive details are in general different and so must both be specified in the argument lists

• Note that the sendcount (at the root) is the number of elements to send to each process, not to send in total.Therefore if sendtype = recvtype, sendcount = recvcount.

• The sendbuf, sendcount, sendtype arguments are significant only at the root

41

MPI_SCATTER ExamplePROGRAM scatter INCLUDE 'mpif.h' INTEGER :: err, rank, size, sendcount, recvcount=1 REAL :: param(8), myparam CALL MPI_INIT(err) CALL MPI_COMM_RANK(MPI_COMM_WORLD, myrank, err) CALL MPI_COMM_SIZE(MPI_COMM_WORLD, nbproc, err) if( myrank.eq.(nbproc-1) ) do i = 1 , 8 param(i) = 100. + i end do sendcount = 1 end if call MPI_SCATTER( param, sendcount, MPI_REAL, & myparam, recvcount, MPI_REAL, & (nbproc-1), MPI_COMM_WORLD, err) print *, 'On proc', myrank, 'myparam =', myparam CALL MPI_FINALIZE(err)END PROGRAM scatter

42

MPI_GATHER

43

MPI_GATHER• MPI_GATHER( sendbuf, sendcount, sendtype,

recvbuf, recvcount, recvtype, root, comm, err)

• The argument list is the same as for MPI_SCATTER

• Specify a root process and all processes must specify the same root (and communicator)

• Note that the recvcount (at the root) is the number of elements to be received from each process, not in total. Therefore if sendtype = recvtype , sendcount = recvcount

• The recvbuf , recvcount , recvtype arguments are significant only at the root

• datas in recvbuf are held by rank order

44

MPI_GATHER ExamplePROGRAM gather INCLUDE 'mpif.h' INTEGER :: err, myrank, nbproc, sendcount=1, recvcount REAL :: param(8), myparam CALL MPI_INIT(err) CALL MPI_COMM_RANK(MPI_COMM_WORLD, myrank, err) CALL MPI_COMM_SIZE(MPI_COMM_WORLD, nbproc, err) myparam = 101. + myrank if( myrank.eq.(nbproc-1) ) recvcount=1 call MPI_GATHER( myparam, sendcount, MPI_REAL, & param, recvcount, MPI_REAL, & (nbproc-1), MPI_COMM_WORLD, err) if( myrank.eq.(nbproc-1) ) do i = 1 , 8 print *,'On proc', myrank, 'param(', i, ') =', param(i) end do end if CALL MPI_FINALIZE(err)END PROGRAM gather

45

10.2. Householder Deflation 619

Remarks

• MPI Alltoall is a collective operation (i.e., it should be called by all processes withinthe communicator).

• Both the sendbuf and recvbuf arrays are relevant on all processes in the communicator.

• In most cases the sendtype and recvtype are identical and the value of sendcount and thevalue of recvcount are identical. MPI requires that the amount of data sent (sendcounttimes the size in bytes of the datatype sendtype) equals the amount of data received(recvcount times the size in bytes of the datatype recvtype) per process/root pair.

• The allocated size of both the sendbuf and recvbuf arrays should be at least equal tothe value of recvtype times the number of processes (totalnodes).

Process 0

senddata

Process 1

Process 2

x00 x01 x02 x03 x04 x05

x10 x11 x12 x13 x14 x15

x20 x21 x22 x23 x24 x25

recvdata

x00 x01 x10 x11 x20 x21

x02 x03 x12 x13 x22 x23

x04 x05 x14 x15 x24 x25

Figure 10.1: MPI Alltoall schematic demonstrating data distribution to all processes of two dataobjects from each process.

We now present an MPI program to accomplish one iteration of the previously presentedHouseholder deflation algorithm. In this program, we assume that the size of the matrix isdivisible by the number of processes used. For the purpose of this example, we will once againuse the Vandermonde matrix formed at the Chebyshev points. It will be distributed by rowsacross the processes (each process forming only those rows which it needs). Observe thatwe will once again use MPI Allreduce and MPI Allgather (as part of the power methodalgorithm), and that we introduce the use of MPI Alltoall. We now present the source codefor this program, and will provide some remarks following it.

#include <iostream.h>#include <iomanip.h>#include "SCmathlib.h"#include "SCchapter3.h"#include<mpi.h>

void ChebyVandermonde(int npts, double *A, int row);

// Global variable to set size of the systemconst int size = 10;

MPI_ALLTOALL

data distribution to all processes of two data objects from each process

MPI_ALLTOALL( sendbuf, sendcount, sendtype, recvbuf, recvcount, recvtype, comm, err)

46

Back to Sum of the first N Integers! parallel solutionprogram sumpar1 include 'mpif.h' integer :: err, myrank, nbproc, status(MPI_STATUS_SIZE) integer :: startval, endval, N=1000, i, partsum, tmpsum call MPI_INIT(ierr) call MPI_COMM_RANK( MPI_COMM_WORLD , myrank, err ) call MPI_COMM_SIZE( MPI_COMM_WORLD , nbproc , err ) startval = N * myrank / nbproc + 1 endval = N * (myrank+1) / nbproc partsum = 0 ; tmpsum = 0 do i = startval, endval partsum = partsum + i end do print * , "partial sum from", startval, "to", endval, & "on proc", myrank, "equals", partsum

47

Back to Sum of the first N Integers if( myrank.ne.0 ) then call MPI_SEND( partsum, 1, MPI_INTEGER, & 0, 23,MPI_COMM_WORLD, err ) else do i = 1 , nproc - 1 call MPI_RECV( tmpsum, 1, MPI_INTEGER, & i, 23, MPI_COMM_WORLD, status, err) partsum = partsum + tmpsum enddo endif if( myrank.eq. 0 ) then print *, "The sum from 1 to", N, "is:", partsum endif call MPI_FINALIZE(err)end program sumpar1

48

Sum of the first N Integers: MPI_REDUCE

call MPI_REDUCE( partsum, tmpsum, 1, MPI_INTEGER, & MPI_SUM, 0, MPI_COMM_WORLD, err )

if( myrank.eq. 0 ) then print *, "The sum from 1 to", N, "is:", tmpsum endif call MPI_FINALIZE(err)end program sumpar1

49

MPI_REDUCE

Collective Communication


7.3.3 MPI_REDUCE

This is illustrated in Figure 25:.

Figure 25: Global reduction in MPI with MPI_REDUCE. o represents the reduction operator.The circles represent processes with ranks as shown. The small boxes represent buffer space andthe letters represent data items. After the routine call, the light-shaded boxes represent buffer

space with undefined contents, the dark-shaded boxes represent the result on the root. Only oneof the four results is illustrated, namely A o E o I o M o Q, but the other four are similar --- forexample, the next element of the result is B o F o J o N o R. Receive buffers are represented by

the empty boxes on the ``before'' side, send buffers by the full boxes.

MPI_REDUCE (sendbuf, recvbuf, count, datatype, op, root, comm)

All processes in the communicator must call with identical arguments other thansendbuf and recvbuf. See “Operators” on page 45 for a description of what to spec-ify for the operator handle. Note that the root process ends up with an array ofresults — if, for example, a total sum is sought, the root must perform the final sum-mation.

7.3.4 Operators

Reduction operators can be predefined or user-defined. Each operator is only valid fora particular datatype or set of datatypes.

7.3.4.1 Predefined operators

These operators are defined on all the obvious basic C and Fortran datatypes (seeTable 7:). The routine MPI_MAXLOC (MPI_MINLOC) allows both the maximum (mini-mum) and the rank of the process with the maximum (minimum) to be found. See

1

2

3

4

RANK

ROOT

A B C D

MPI_REDUCE

0

Q R S T

F G HE F

K LI NJ

PM N NO

A B C D

Q R S T

F G HE F

K LI NJ

PM N NO

AoEoIoMoQ

50


46 Course notes

“Global reduction operations in MPI” on page 43. More details with examples can befound in the MPI document [1].

7.3.4.2 User-defined operators

To define his or her own reduction operator, in C the user must write the operator as afunction of type MPI_User_function which is defined thus:

typedef void MPI_User_function (void *invec, void *inoutvec, int

*len, MPI_Datatype *datatype);

while in Fortran the user must write an EXTERNAL subroutine of the following type

SUBROUTINE USER_FUNCTION (INVEC(*), INOUTVEC(*), LEN, TYPE)

<type> INVEC(LEN), INOUTVEC(LEN)

INTEGER LEN, TYPE

The operator must be written schematically like this:

for(i = 1 to len)

inoutvec(i) = inoutvec(i) o invec(i)

where o is the desired operator. When MPI_REDUCE (or another reduction routine iscalled), the operator function is called on each processor to compute the global resultin a cumulative way. Having written a user-defined operator function, it has to be reg-istered with MPI at run-time by calling the MPI_OP_CREATE routine.

MPI_OP_CREATE (function, commute, op)

Table 7: Predefined operators

MPI Name Function

MPI_MAX Maximum

MPI_MIN Minimum

MPI_SUM Sum

MPI_PROD Product

MPI_LAND Logical AND

MPI_BAND Bitwise AND

MPI_LOR Logical OR

MPI_BOR Bitwise OR

MPI_LXOR Logical exclusive OR

MPI_BXOR Bitwise exclusive OR

MPI_MAXLOC Maximum & location

MPI_MINLOC Minimum & location

51

• Exemple of Global Reduction Operation

• MPI_REDUCE( senbuf, recvbuf, count, datatype, operation, root, comm, error )

• All processes must specify the same root (and communicator).

• Possibility to define your own reduction operation acting on your own datatype ...

• The operation must be associative (evaluation order doesn't account)

52

MPI_REDUCE

Collective Communication


These return the operator handle op, suitable for use in global reduction calls. If theoperator is commutative (A o B = B o A) — the value commute should be specified asTRUE, as it may allow MPI to perform the reduction faster.

7.3.5 MPI_ALLREDUCE, MPI_REDUCE_SCATTER,MPI_SCAN

These are variants of MPI_REDUCE. They are illustrated in Figure 26:,

Figure 26: Global reduction in MPI with MPI_ALLREDUCE. The symbols are as in Figure25:. The only difference from MPI_REDUCE is that there is no root --- all processes receive the

result.

1

2

3

4

RANK

A B C D

0

Q R S T

F G HE F

K LI NJ

PM N NO

A B C D

Q R S T

F G HE F

K LI NJ

PM N NO

MPI_ALLREDUCE

AoEoIoMoQ

53

(No Root)

54

MPI_ALLREDUCE

55

Communication Modes•The standard MPI_SEND call is blocking :

it does not return until the message data and envelope have been safely stored away so that the sender is free to modify the send buffer.

•“Completion” of a send means by definition that the send buffer can safely be re-used.

•The message might be copied directly into the matching receive buffer, or it might be copied into a temporary system buffer.

•To be continued, see good References next slide

56

Communication Modes•References:

‣Standard Send and Recv:http://www.mpi-forum.org/docs/mpi22-report/node41.htm#Node41

‣Communication Modes:http://www.mpi-forum.org/docs/mpi22-report/node53.htm#Node53

‣"MPI par l'exemple" : http://algernon.cism.ucl.ac.be/mpi/mpi.html

‣epcc "Writing Message Passing Parallel Programs with MPI" http://www.rz.uni-karlsruhe.de/rz/docs/MPI/epcc-course.html Section 3.2 page 9

http://www.mpi-forum.org/docs/mpi22-report/node41.htm%23Node41




http://algernon.cism.ucl.ac.be/mpi/mpi.html


http://www.rz.uni-karlsruhe.de/rz/docs/MPI/epcc-course.html


57

MPI Tips

• Load Balancing: Distribute evenly the work among all the processes

• Minimize the communication: Because of the latency, even a zero-byte message takes an uncompressible minimum time.

• Superpose/Mix calculation and communication

58

MPI References• MPI standard :

http://www.mpi-forum.org/

• MPICH1 : http://www.mcs.anl.gov/research/projects/mpi/mpich1/

• MPICH2 : http://www.mcs.anl.gov/research/projects/mpich2/

• Open-MPI : http://www.open-mpi.org/

• Where can I learn about MPI ? Are there tutorials available ?http://www.open-mpi.org/faq/?category=general#tutorials

• Writing Message-Passing Parallel Programs with MPI :http://www.rz.uni-karlsruhe.de/rz/docs/MPI/epcc-course.html

• "MPI par l'exemple" : http://algernon.cism.ucl.ac.be/mpi/mpi.html



http://www.mcs.anl.gov/research/projects/mpi/mpich1/

http://www.mcs.anl.gov/research/projects/mpi/mpich1/

http://www.mcs.anl.gov/research/projects/mpich2/

http://www.mcs.anl.gov/research/projects/mpich2/

http://www.open-mpi.org/

http://www.open-mpi.org/

http://www.open-mpi.org/faq/?category=general%23tutorials

http://www.open-mpi.org/faq/?category=general%23tutorials





59

Documents

MPI - Montefiore Institutemontefiore.ulg.ac.be/~geuzaine/INFO0939/MPI.pdf · Tips & Tricks • Questions: Which compilers are available ? Where ? ... ‣ buffer (start of the memory