Commit 7286e94f authored by Pavan Balaji's avatar Pavan Balaji
Browse files

[svn-r10787] Fix instances where we say MPI-2, and use generic "MPI" where possible

so we don't have to keep correcting this.  Also removed section
numbers from the MPI-2 standard that were referenced in the ROMIO
documents.  If we feel that they are necessary, we can add them back
after the release.

No reviewer.
parent b8d1cfa1
......@@ -185,10 +185,10 @@ shared memory), Hydra process management) of MPICH up and running.
process managers; the default is called Hydra.
Now we will run an MPI job, using the mpiexec command as specified
in the MPI-2 standard. There are some examples in the install
in the MPI standard. There are some examples in the install
directory, which you have already put in your path, as well as in
the directory mpich-%VERSION%/examples. One of them is the
classic CPI example, which computes the value of pi by numerical
the directory mpich-%VERSION%/examples. One of them is the classic
CPI example, which computes the value of pi by numerical
integration in parallel.
To run the CPI example with 'n' processes on your local machine,
......
......@@ -101,7 +101,7 @@ Brian Toonen
\section{Introduction}
\label{sec:intro}
This manual describes how to obtain and install MPICH, the MPI-2
This manual describes how to obtain and install MPICH, the MPI
implementation from Argonne National Laboratory. (Of course, if you are
reading this, chances are good that you have already obtained it and
found this document, among others, in its \texttt{doc} subdirectory.)
......@@ -324,7 +324,7 @@ executable on.
\item
Now we will run an MPI job, using the \texttt{mpiexec} command as specified
in the MPI-2 standard.
in the MPI standard.
As part of the build process for MPICH, a simple program to compute the value
of $\pi$ by numerical integration is created in the
......
......@@ -11,7 +11,7 @@
\section{Introduction}
MPI-2 defines a set of routines for exchanging data with other MPI
MPI defines a set of routines for exchanging data with other MPI
programs. The intent of these is to allow MPI applications to
exchange the data that is needed for the \code{port} argument in the
\code{MPI_Comm_connect} and \code{MPI_Comm_accept} calls.
......@@ -84,7 +84,7 @@ calls. As in other MPI calls, the free routine takes a pointer to the
handle so that the handle can be set to null when the free routine
succeeds. Each of these routines returns either \code{MPI_SUCCESS} or
a valid MPI error code; implementations may either use the MPICH
error code mechanism or, for external packages, use the MPI-2 routines
error code mechanism or, for external packages, use the MPI routines
for adding error codes and classes.
\begin{verbatim}
......@@ -212,4 +212,4 @@ Some of the features, such as \code{NAMEPUB_EXPIRE}, are not supported
by this interface. The info key \code{NAMEPUB_CONTACT} can be used to
specify the directory into which the files will be placed.
\end{document}
\ No newline at end of file
\end{document}
......@@ -61,7 +61,7 @@ man pages (often installed in \file{/usr/local/mpi/man}) or the web pages
\section{MPI routines}
This section contains descriptions of each of the routines in the MPI
standard, including both MPI-1 and MPI-2.
standard.
In the description of the routine parameters, the following terms are
used:
......
......@@ -92,12 +92,12 @@ there should be enough here to get you started with MPICH.
\label{sec:migrating}
MPICH is a high-performance and widely portable implementation of the
MPI Standard, designed to implement all of MPI-1 and MPI-2 (including
dynamic process management, one-sided operations, parallel I/O, and
other extensions). The \emph{MPICH Installer's Guide} provides some
information on MPICH with respect to configuring and installing
it. Details on compiling, linking, and running MPI programs are
described below.
MPI Standard, designed to implement all of MPI-1, MPI-2, and MPI-3
(including dynamic process management, one-sided operations, parallel
I/O, and other extensions). The \emph{MPICH Installer's Guide}
provides some information on MPICH with respect to configuring and
installing it. Details on compiling, linking, and running MPI programs
are described below.
\subsection{Default Runtime Environment}
......@@ -210,7 +210,7 @@ Some users may get error messages such as
\end{small}
The problem is that both \texttt{stdio.h} and the MPI C++ interface use
\texttt{SEEK\_SET}, \texttt{SEEK\_CUR}, and \texttt{SEEK\_END}. This is really a bug
in the MPI-2 standard. You can try adding
in the MPI standard. You can try adding
\begin{verbatim}
#undef SEEK_SET
#undef SEEK_END
......@@ -240,16 +240,16 @@ are not provided.
\section{Running Programs with \texttt{mpiexec}}
\label{sec:mpiexec}
The MPI-2 Standard describes \texttt{mpiexec} as a suggested way to
run MPI programs. MPICH implements the \texttt{mpiexec} standard, and
also provides some extensions.
The MPI Standard describes \texttt{mpiexec} as a suggested way to run
MPI programs. MPICH implements the \texttt{mpiexec} standard, and also
provides some extensions.
\subsection{Standard \texttt{mpiexec}}
\label{sec:mpiexec-standard}
Here we describe the standard \texttt{mpiexec} arguments from the MPI-2
Standard~\cite{mpi-forum:mpi2-journal}. The simplest form of a command
to start an MPI job is
Here we describe the standard \texttt{mpiexec} arguments from the MPI
Standard~\cite{mpi-forum:mpi2-journal}. The simplest form of a
command to start an MPI job is
\begin{verbatim}
mpiexec -f machinefile -n 32 a.out
......@@ -272,7 +272,7 @@ It is also possible to start a one process MPI job (with a
\texttt{mpiexec}. This process will become an MPI process when it
calls \texttt{MPI\_Init}, and it may then call other MPI functions.
Currently, MPICH does not fully support calling the dynamic process
routines from MPI-2 (e.g., \texttt{MPI\_Comm\_spawn} or
routines from the MPI standard (e.g., \texttt{MPI\_Comm\_spawn} or
\texttt{MPI\_Comm\_accept}) from processes that are not started with
\texttt{mpiexec}.
......@@ -306,7 +306,7 @@ It can launch jobs across both platforms if the binary formats match
\subsubsection{\texttt{mpiexec} arguments for SMPD}
\label{sec:mpiexec-smpd}
\texttt{mpiexec} for smpd accepts the standard MPI-2 \texttt{mpiexec}
\texttt{mpiexec} for smpd accepts the standard MPI \texttt{mpiexec}
options. Execute
\begin{verbatim}
mpiexec
......@@ -676,10 +676,10 @@ specified.
\section{Other Tools Provided with MPICH}
\label{sec:other-tools}
MPICH also includes a test suite for MPI-1 and MPI-2 functionality; this
suite may be found in the \texttt{mpich/test/mpi} source directory and can be
run with the command \texttt{make testing}. This test suite should work with
any MPI implementation, not just MPICH.
MPICH also includes a test suite for MPI functionality; this suite may
be found in the \texttt{mpich/test/mpi} source directory and can be
run with the command \texttt{make testing}. This test suite should
work with any MPI implementation, not just MPICH.
\section{MPICH2 under Windows}
\label{sec:windows}
......
......@@ -694,7 +694,7 @@ This flag is used in conjunction with the \texttt{-rsh} flag. With this flag
specified there need not be any smpd process manager running on any of the nodes
used in the job. \texttt{mpiexec} provides the PMI interface and the remote
shell command is used to start the processes. Using these flags allows jobs to
be started without any process managers running but the MPI-2 dynamic process
be started without any process managers running but the MPI dynamic process
functions like MPI\_Comm\_spawn are consequently not available.
\item \texttt{-noprompt}
......@@ -974,7 +974,7 @@ set PMI_ROOT_HOST=%COMPUTERNAME%
to set the variable to the hostname where the root process will be started instead
of the local host name.
The limitation of this method of starting processes is that MPI-2 spawning operations
The limitation of this method of starting processes is that MPI spawning operations
are not supported. If your application calls MPI\_Comm\_spawn it will produce
an error.
......
......@@ -109,7 +109,7 @@ N*/
The sizes of MPI strings in Fortran are one less than the sizes of that
string in C/C++ because the C/C++ versions provide room for the trailing
null character required by C/C++. For example, 'MPI_MAX_ERROR_STRING' is
'mpif.h' is one smaller than the same value in 'mpi.h'. See the MPI-2
'mpif.h' is one smaller than the same value in 'mpi.h'. See the MPI
standard, sections 2.6.2 and 4.12.9.
N*/
......
......@@ -161,9 +161,9 @@ Major Changes in Version 1.0.3:
Major Changes Version 1.0.2:
---------------------------
* Implemented the shared file pointer functions (Section 9.4.4 of MPI-2) and
split collective I/O functions (Section 9.4.5). Therefore, the main
components of the MPI-2 I/O chapter not yet implemented are
* Implemented the shared file pointer functions and
split collective I/O functions. Therefore, the main
components of the MPI I/O chapter not yet implemented are
file interoperability and error handling.
* Added support for using "direct I/O" on SGI's XFS file system.
......@@ -298,13 +298,13 @@ General Information
-------------------
ROMIO is a high-performance, portable implementation of MPI-IO (the
I/O chapter in MPI-2). ROMIO's home page is at
http://www.mcs.anl.gov/romio . The MPI-2 standard is available at
I/O chapter in MPI). ROMIO's home page is at
http://www.mcs.anl.gov/romio . The MPI standard is available at
http://www.mpi-forum.org/docs/docs.html .
This version of ROMIO includes everything defined in the MPI-2 I/O
chapter except support for file interoperability (Sec. 9.5 of MPI-2) and
user-defined error handlers for files (Sec. 4.13.3). The subarray and
This version of ROMIO includes everything defined in the MPI I/O
chapter except support for file interoperability and
user-defined error handlers for files. The subarray and
distributed array datatype constructor functions from Chapter 4
(Sec. 4.14.4 & 4.14.5) have been implemented. They are useful for
accessing arrays stored in files. The functions MPI_File_f2c and
......@@ -587,7 +587,7 @@ Use a larger number if you still get the error message.
* If a Fortran program uses a file handle created using ROMIO's C
interface, or vice-versa, you must use the functions MPI_File_c2f
or MPI_File_f2c (see MPI-2 Section 4.12.4). Such a situation occurs,
or MPI_File_f2c. Such a situation occurs,
for example, if a Fortran program uses an I/O library written in C
with MPI-IO calls. Similar functions MPIO_Request_f2c and
MPIO_Request_c2f are also provided.
......
......@@ -95,7 +95,7 @@ by \\ [2ex]
\begin{abstract}
\noindent
ROMIO is a high-performance, portable implementation of MPI-IO (the
I/O chapter in \mbox{MPI-2}).
I/O chapter in the \mbox{MPI Standard}).
This document describes the internals of the ROMIO implementation.
\end{abstract}
......@@ -121,7 +121,7 @@ where those components are located in the ROMIO source tree.
The ROMIO directory structure consists of two main branches, the MPI-IO branch
(mpi-io) and the ADIO branch (adio). The MPI-IO branch contains code that
implements the functions defined in the MPI-2 specification for I/O, such as
implements the functions defined in the MPI specification for I/O, such as
MPI\_File\_open. These functions are then written in terms of other functions
that provide an abstract interface to I/O resources, the ADIO functions.
There is an additional glue subdirectory in the MPI-IO branch that defines
......@@ -369,7 +369,7 @@ Currently ROMIO implements shared file pointers by storing the file pointer
value in a separate file...
Note that the ROMIO team has devised a portable method for implementing shared
file pointers using only MPI-1 and MPI-2 functions. However, this method has
file pointers using only MPI functions. However, this method has
not yet been implemented in ROMIO.
file name is selected at end of mpi-io/open.c.
......
......@@ -94,7 +94,7 @@ by \\ [2ex]
\begin{abstract}
\noindent
ROMIO is a high-performance, portable implementation of MPI-IO (the
I/O chapter in \mbox{MPI-2}). This document describes how to install and use
I/O chapter in the \mbox{MPI Standard}). This document describes how to install and use
ROMIO version~1.2.4 on various machines.
\end{abstract}
......@@ -102,7 +102,7 @@ ROMIO version~1.2.4 on various machines.
ROMIO\footnote{\tt http://www.mcs.anl.gov/romio} is a
high-performance, portable implementation of MPI-IO (the I/O chapter in
MPI-2~\cite{mpi97a}). This document describes how to install and use
MPI~\cite{mpi97a}). This document describes how to install and use
ROMIO version~1.2.4 on various machines.
......@@ -124,8 +124,8 @@ ROMIO version~1.2.4 on various machines.
%
\section{General Information}
This version of ROMIO includes everything defined in the MPI-2 I/O
chapter except support for file interoperability (\S~9.5 of MPI-2) and
This version of ROMIO includes everything defined in the MPI I/O
chapter except support for file interoperability and
user-defined error handlers for files (\S~4.13.3). The subarray and
distributed array datatype constructor functions from Chapter 4
(\S~4.14.4 \& \S~4.14.5) have been implemented. They are useful for
......@@ -324,7 +324,7 @@ these collective buffering hints). Further, in the ROMIO implementation
the hint is only recognized at \texttt{MPI\_File\_open} time.
The set of hints used with a file is available through the routine
\texttt{MPI\_File\_get\_info}, as documented in the MPI-2 standard.
\texttt{MPI\_File\_get\_info}, as documented in the MPI standard.
As an additional feature in the ROMIO implementation, wildcards will
be expanded to indicate the precise configuration used with the file,
with the hostnames in the rank order used for the collective buffering
......@@ -654,7 +654,7 @@ the ADIO implementation in order to get the specific output they desire.
\subsection{ROMIO and {\tt MPI\_FILE\_SYNC}}
The MPI-2 specification notes that a call to {\tt MPI\_FILE\_SYNC} ``causes
The MPI specification notes that a call to {\tt MPI\_FILE\_SYNC} ``causes
all previous writes to {\tt fh} by the calling process to be transferred to
the storage device.'' Likewise, calls to {\tt MPI\_FILE\_CLOSE} have this
same semantic. Further, ``if all processes have made updates to the storage
......@@ -1002,9 +1002,9 @@ therefore used as the default.
\subsection{Major Changes in Version 1.0.2}
\begin{itemize}
\item Implemented the shared file pointer functions (\S~9.4.4 of MPI-2) and
split collective I/O functions (\S~9.4.5). Therefore, the main
components of the MPI-2 I/O chapter not yet implemented are
\item Implemented the shared file pointer functions and
split collective I/O functions. Therefore, the main
components of the MPI I/O chapter not yet implemented are
file interoperability and error handling.
\item Added support for using ``direct I/O'' on SGI's XFS file system.
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment