MPI Examples
A.1 “Hello world”
A quick application to test the MPI libraries and the network.
A.2 MPI Skeleton
The sample code below contains the complete communications skeleton for a dynamically load balanced head/compute node application. Following the code is a description of some of the functions necessary for writing typical parallel applications.
Processes are represented by a unique rank (integer) and ranks are numbered 0, 1, 2, …, N-1. MPI_COMM_WORLD means all the processes in the MPI application. It is called a communicator and it provides all information necessary to do message passing. Portable libraries do more with communicators to provide synchronisation protection that most other systems cannot handle.
A.3 MPI Initialization And Finalization
As with other systems, two functions are provided to initialize and clean up an MPI process:
A.4 What Is The Current Process? How Many Processes Are There?
Typically, a process in a parallel application needs to know who it is (its rank) and how many other processes exist.
A process finds out its own rank by calling:
The total number of processes is returned by MPI_Comm_size( ):
A.5 Sending Messages
A message is an array of elements of a given data type. MPI supports all the basic data types and allows a more elaborate application to construct new data types at runtime. A message is sent to a specific process and is marked by a tag (integer value) specified by the user. Tags are used to distinguish between different message types a process might send/receive. In the sample code above, the tag is used to distinguish between work and termination messages.
A.6 Receiving Messages
A receiving process specifies the tag and the rank of the sending process. MPI_ANY_TAG and MPI_ANY_SOURCE may be used optionally to receive a message of any tag and from any sending process.
Information about the received message is returned in a status variable. The received message tag is status.MPI_TAG and the rank of the sending process is status.MPI_SOURCE. Another function, not used in the sample code, returns the number of data type elements received. It is used when the number of elements received might be smaller than maxcount.
A.7 Blocking, Non-Blocking, And Persistent Messages
MPI_Send and MPI_Receive cause the running program to wait for non-local communication from a network. Most communication networks function at least an order of magnitude slower than local computations. When an MPI process has to wait for non-local communication CPU cycles are lost because the operating system has to block the process, then has to wait for communication, and then resume the process.
An optimal efficiency is usually best achieved by overlapping communication and computation. Blocking messaging functions only allow one communication to occur at a time. Non-blocking messaging functions allow the application to initiate multiple communication operations, enabling the MPI implementation to proceed simultaneously. Persistent non-blocking messaging functions allow a communication state to persist, so that the MPI implementation does not waste time on initializing or terminating a communication.
A.7.1 Blocking Messages
In the following example, the communication implementation executes in a sequential fashion causing each process, MPI_Recv, then MPI_Send, to block while waiting for its neighbor:
Example
MPI also has the potential to allow both communications to occur simultaneously, as in the following communication implementation example:
A.7.2 Non-Blocking Messages
Example
In the example, MPI_Waitall potentially allows both communications to occur simultaneously. However, the process as show is blocked until both communications are complete.
A.7.3 Persistent, Non-Blocking Messages
A more efficient use of the waiting time means to carry out some other work in the meantime that does not depend on that communication. If the same buffers and communication parameters are to be used in each iteration, then a further optimization is to use the MPI persistent mode. The following code instructs MPI to set up the communications once, and communicate similar messages every time:
Example
In the example, MPI_Send_init and MPI_Recv_init perform a persistent communication initialization.