Scientific Computing & Visualization
Help Contact
About Accounts Computation Visualization Documentation Services

Multiprocessing by Message Passing MPI

Example 1.5 Integration with MPI Collective Communications

Associative and Commutative Rules

An operator ¤ satifies the associative rule if:
a ¤ (b ¤ c) = (a ¤ b) ¤ c

For example, addition (+) satisfies the associative rule but subtraction (-) does not.

An operator ¤ satisfies the commutative rule if:
a ¤ b = b ¤ a

For example, multiplication (*) satisfies the commutative rule but division (/) does not.

Starts MPI on a processor. It must be called only once in the entire program. If no error, ierr returns 0.

Querry for the identity of the current processor, myid. Knowing myid, the user program may act on different data or different tasks accordingly. For this example, it is used to determine the range of integration and hence each processor acts on its own data (see ai). In addition, the total integral sum is computed only on the process with myid = 0.

A communicator dictates which processes can participate in a message passing operation. MPI_COMM_WORLD is a commonly used communicator pre-defined in mpif.h (for fortran) or mpi.h (for C). It enables all processes to participate in message passing operations such as MPI_Recv. On the other hand, a programmer can define a communicator which restricts accessibility to specific (e.g., odd or even numbered) processors for any message passing operation that requires it.

A communicator has type INTEGER.
Buffer, buffer size, data type

All MPI message passing routines, such as MPI_Send and MPI_Recv, require these three arguments to define the (send or receive) buffer, its size, and MPI data type. Examples of MPI data types are:
MPI_REAL, MPI_INTEGER, MPI_CHARACTER

Querry for the number of processors. This is provided by the user at runtime to the executable a.out via the command
katana% mpirun -np 4 a.out

In this example, MPI_Comm_size returns p = 4.

Exit MPI. Like MPI_Init, this routine should only be called once in the entire program, after all MPI parallel processing is done.

Performs point-to-point blocking send. The call to this routine continue to block until the send buffer can be safely overwritten (i.e., the content of the send buffer has been received at the destination).

Performs point-to-point blocking receive. The call to this routine continue to block until the receive buffer contains the intended data (or message).

Performs point-to-point nonblocking send. The send buffer should not be overwritten until the operation is confirmed to be complete by way of MPI_Wait.

Block until the operation (in this case, signaled by request arising from MPI_Isend) is completed.
Message Source

It tells the receiver where the message comes from.

MPI_ANY_SOURCE is a constant pre-defined in mpif.h. This represents a source (processor) "wild card."

For the parallel numerical integration example, the integration is the sum of all partial integral sums from all processors. Because summation is an operation that satisfies the associative rule which means the result is not dependent on any specific order of summation, the use of MPI_ANY_SOURCE can potentially be more efficient (first come first served) as well as less likely to deadlock. When a message is received with MPI_ANY_SOURCE, the source can be retrieved via status(MPI_SOURCE).
Message Destination

It tells the sender where to send the message.
Message Tag

Tag serves as a secondary means to define the identity of a message. The primary means is the processor rank, myid.
Message Status

Returns the status of a message receive operation. This contains information about where the message came from and its tag when wild cards MPI_ANY_SOURCE and MPI_ANY_TAG are used as source and tag, respectively.

The status is declared "integer status(MPI_STATUS_SIZE)".

MPI_ANY_TAG is a constant pre-defined in mpif.h. This represents a tag "wild card." Generally, a tag is used as a secondary means to identify a message -- the primary means is myid. An example that requires a tag in addition to myid is when multiple messages are passed between a pair of processors. Upon receive of these messages, if the receiver needs to distinguish the identities of them in order to place them or act on them accordingly, then tag can be used to differentiate the messages. When a message is received with MPI_ANY_TAG, the tag can be retrieved via status(MPI_TAG).
Compute integral with range defined by i (i.e., process myid).

real function integral(ai, h, n)
implicit none
integer n, j
real h, ai, aij

integral = 0.0         ! initialize integral
do j=0,n-1             ! sum integrals
  aij = ai + (j+0.5)*h ! abscissa mid-point
  integral = integral + cos(aij)*h
enddo

return
end

Starts MPI on a processor. It must be called only once in the entire program. All MPI C functions return an error flag. If no error, ierr returns 0.

Querry for the identity of the current processor, myid. Knowing myid, the user program may act on different data or different tasks accordingly. For this example, it is used to determine the range of integration and hence each processor acts on its own data (see ai). In addition, the total integral sum is computed only on the process with myid = 0.

A communicator dictates which processes can participate in a message passing operation. MPI_COMM_WORLD is a commonly used communicator pre-defined in mpif.h (for fortran) or mpi.h (for C). It enables all processes to participate in message passing operations such as MPI_Recv. On the other hand, a programmer can define a communicator which restricts accessibility to specific (e.g., odd or even numbered) processors for any message passing operation that requires it.

A communicator has type MPI_Comm.
Buffer, buffer size, data type

All MPI message passing routines, such as MPI_Send and MPI_Recv, require these three arguments to define the (send or receive) buffer, its size, and MPI data type. Examples of MPI data types are:
MPI_FLOAT, MPI_INT, MPI_CHAR

Querry for the number of processors. This is provided by the user at runtime to the executable a.out via the command
katana% mpirun -np 4 a.out

In this example, MPI_Comm_size returns p = 4.

Exit MPI. Like MPI_Init, this routine should only be called once in the entire program, after all MPI parallel processing is done.

Performs point-to-point blocking send. The call to this routine continue to block until the send buffer can be safely overwritten (i.e., the content of the send buffer has been received at the destination).

Performs point-to-point blocking receive. The call to this routine continue to block until the receive buffer contains the intended data (or message).

Performs point-to-point nonblocking send. The send buffer should not be overwritten until the operation is confirmed to be complete by way of MPI_Wait.

Block until the operation (in this case, signaled by request arising from MPI_Isend) is completed.
Message Destination

It tells the sender where to send the message.
Message Source

It tells the receiver where the message comes from.

MPI_ANY_SOURCE is a constant pre-defined in mpi.h. This represents a source (processor) "wild card."

For the parallel numerical integration example, the integration is the sum of all partial integral sums from all processors. Because summation is an operation that satisfies the associative rule which means the result is not dependent on any specific order of summation, the use of MPI_ANY_SOURCE can potentially be more efficient (first come first served) as well as less likely to deadlock. When a message is received with MPI_ANY_SOURCE, the source can be retrieved via status.MPI_SOURCE.
Message Tag

Tag serves as a secondary means to define the identity of a message. The primary means is the processor rank, myid.

MPI_ANY_TAG is a constant pre-defined in mpi.h. This represents a tag "wild card." Generally, a tag is used as a secondary means to identify a message -- the primary means is myid. An example that requires a tag in addition to myid is when multiple messages are passed between a pair of processors. Upon receive of these messages, if the receiver needs to distinguish the identities of them in order to place them or act on them accordingly, then tag can be used to differentiate the messages. When a message is received with MPI_ANY_TAG, the tag can be retrieved via status.MPI_TAG.
Message Status

Returns the status of a message receive operation. This contains information about where the message came from and its tag when wild cards MPI_ANY_SOURCE and MPI_ANY_TAG are used as source and tag, respectively.

This is declared with "MPI_Status status".
Compute integral with range defined by i (i.e., process myid).

float integral(float ai, float h, int n)
{
 int j;
 float aij, integ;

 integ = 0.0;            /* initialize */
 for (j=0;j<n;j++) {  /* sum integrals */
   aij = ai + (j+0.5)*h; /* mid-point */
   integ += cos(aij)*h;
 } 
 return integ;
}

So far, we have used point-to-point blocking and nonblocking communication routines to perform numerical integration. In this example, we turn our focus to collective communication routines. Unlike point-to-point communications with which a message is passed between one processor and another, a collective communication routine performs a one (processor) to all (processors) , all-to-one, or all-to-all communications. Broadcasting is a typical example of a one-to-all communication while a gather operation is representative of an all-to-one communication.

Two collective communication routines are introduced in this example. First, we make the program more general by allowing the number of intervals, n, for each sub-range to be defined through run-time input. To avoid repetition, it is read on the master processor only. To make n available on all processors, it must then be copied to all processes. This can be accomplished with a broadcast operation, MPI_Bcast. In previous examples, after the local integral sums have been computed by all participating processes, they are individually sent to the master who sums them to obtain the final sum. In this example, a collective reduction routine, MPI_Reduce, will be used to perform the same task. As you will see, they are more compact and convenient to use than point-to-point communication routines, they are also expected to be more efficient and less prone to errors.

Example 1.5 Fortran code

Example 1.5 C code

Discussions

All collective communication routines are implemented so that the call to the routine must be invoked on all processes. For MPI_Bcast, the source of the broadcast is master. On this process, MPI_Bcast acts as a send. On all other processes where myid is not master, it automatically knows that it must act as a receive.

Once my_int is computed on all processes, calling the collective reduction subroutine MPI_Reduce will take care of collecting my_int from all processes followed by a reduction (summation) operation. Reduction operation can be one of two types: pre-defined or user-defined. Pre-defined reduction operations are built in to MPI and include, for example : MPI_SUM for summing; MPI_MAX and MPI_MIN for finding extremums; MPI_MAXLOC and MPI_MINLOC for finding extremums and their corresponding locations. In order to use MPI_Reduce, the reduction operation must satisfy the associative rule. If it also satisfies the commutative rule, the reduction operation may gain in efficiency. For example, summation, or MPI_SUM, is a reduction operator that is both associative and commutative. Subtraction, which is not on the list of pre-defined reduction operations, is neither associative nor commutative. User-defined reduction operations must also satisfy the associative rule and optionally the commutative rule. For further details, see MPI: The Complete Reference.

Example 1  | Example 1.1 | Example 1.2 | Example 1.3 | Example 1.4 | Example 1.5

Boston University
Boston University
 
OIT | CCS | July 17, 2008  
Scientific Computing & Visualization Boston University home page Boston University home page