mpich2-1.4.1p1
所属分类:超算/并行计算
开发工具:Visual C++
文件大小:22827KB
下载次数:19
上传日期:2012-05-28 14:23:09
上 传 者:
candy8721
说明: mpi的源码,示例程序等,主要用于对mpi并行编程程序的研究。
(mpi source code, sample programs, mainly for mpi parallel programming procedures.)
文件列表:
mpich2-1.4.1p1 (0, 2012-02-07)
mpich2-1.4.1p1\CHANGES (52140, 2011-08-24)
mpich2-1.4.1p1\confdb (0, 2012-02-07)
mpich2-1.4.1p1\confdb\aclocal.m4 (1513, 2011-03-12)
mpich2-1.4.1p1\confdb\aclocal_am.m4 (359, 2010-07-15)
mpich2-1.4.1p1\confdb\aclocal_atomic.m4 (7559, 2007-11-03)
mpich2-1.4.1p1\confdb\aclocal_attr_alias.m4 (19001, 2010-12-07)
mpich2-1.4.1p1\confdb\aclocal_bugfix.m4 (2667, 2010-09-03)
mpich2-1.4.1p1\confdb\aclocal_cache.m4 (13031, 2010-08-25)
mpich2-1.4.1p1\confdb\aclocal_cc.m4 (50518, 2011-03-24)
mpich2-1.4.1p1\confdb\aclocal_cxx.m4 (5195, 2011-03-12)
mpich2-1.4.1p1\confdb\aclocal_f77.m4 (43961, 2011-04-22)
mpich2-1.4.1p1\confdb\aclocal_f77old.m4 (13162, 2011-03-12)
mpich2-1.4.1p1\confdb\aclocal_fc.m4 (29976, 2011-06-19)
mpich2-1.4.1p1\confdb\aclocal_libs.m4 (3284, 2011-04-13)
mpich2-1.4.1p1\confdb\aclocal_make.m4 (7982, 2010-07-15)
mpich2-1.4.1p1\confdb\aclocal_mpi.m4 (16214, 2011-03-05)
mpich2-1.4.1p1\confdb\aclocal_romio.m4 (24184, 2011-03-12)
mpich2-1.4.1p1\confdb\aclocal_runlog.m4 (8606, 2011-03-12)
mpich2-1.4.1p1\confdb\aclocal_shl.m4 (14998, 2010-09-01)
mpich2-1.4.1p1\confdb\aclocal_subcfg.m4 (5581, 2010-12-07)
mpich2-1.4.1p1\confdb\aclocal_util.m4 (5708, 2010-12-07)
mpich2-1.4.1p1\confdb\ax_prefix_config_h.m4 (9152, 2009-06-16)
mpich2-1.4.1p1\confdb\ax_tls.m4 (3246, 2010-05-18)
mpich2-1.4.1p1\confdb\config.guess (44941, 2010-08-09)
mpich2-1.4.1p1\confdb\config.sub (34423, 2010-08-09)
mpich2-1.4.1p1\confdb\depcomp (18615, 2009-10-28)
mpich2-1.4.1p1\confdb\install-sh (13663, 2009-06-30)
mpich2-1.4.1p1\confdb\missing (11419, 2009-10-28)
mpich2-1.4.1p1\configure (1481453, 2011-09-02)
mpich2-1.4.1p1\configure.in (234727, 2011-08-16)
mpich2-1.4.1p1\contrib (0, 2012-02-07)
mpich2-1.4.1p1\contrib\knem (0, 2012-02-07)
mpich2-1.4.1p1\contrib\knem\knem-0.5.0.tar.gz (89459, 2009-04-28)
mpich2-1.4.1p1\COPYRIGHT (1937, 2011-03-02)
mpich2-1.4.1p1\COPYRIGHT.rtf (8076, 2009-02-28)
mpich2-1.4.1p1\doc (0, 2012-02-07)
mpich2-1.4.1p1\doc\design (0, 2012-02-07)
... ...
MPICH2 Release 1.4.1p1
MPICH2 is a high-performance and widely portable implementation of the
MPI-2.2 standard from the Argonne National Laboratory. This release
has all MPI 2.2 functions and features required by the standard with
the exception of support for the "external32" portable I/O format and
user-defined data representations for I/O.
The distribution has been tested by us on a variety of machines in our
environments as well as our partner institutes. If you have problems
with the installation or usage of MPICH2, please send an email to
mpich-discuss@mcs.anl.gov (you need to subscribe to this list
(https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss) before
sending an email). If you have found a bug in MPICH2, we request that
you report it at our bug tracking system:
(https://trac.mcs.anl.gov/projects/mpich2/newticket).
This README file should contain enough information to get you started
with MPICH2. More extensive installation and user guides can be found
in the doc/installguide/install.pdf and doc/userguide/user.pdf files
respectively. Additional information regarding the contents of the
release can be found in the CHANGES file in the top-level directory,
and in the RELEASE_NOTES file, where certain restrictions are
detailed. Finally, the MPICH2 web site,
http://www.mcs.anl.gov/research/projects/mpich2, contains information
on bug fixes and new releases.
1. Getting Started
2. Compiler Flags
3. Alternate Channels and Devices
4. Alternate Process Managers
5. Alternate Configure Options
6. Testing the MPICH2 installation
7. Fault Tolerance
8. Environment Variables
9. Developer Builds
10. Installing MPICH2 on windows
11. Multiple Fortran compiler support
-------------------------------------------------------------------------
1. Getting Started
==================
The following instructions take you through a sequence of steps to get
the default configuration (ch3 device, nemesis channel (with TCP and
shared memory), Hydra process management) of MPICH2 up and running.
(a) You will need the following prerequisites.
- REQUIRED: This tar file mpich2-1.4.1p1.tar.gz
- REQUIRED: A C compiler (gcc is sufficient)
- OPTIONAL: A C++ compiler, if C++ applications are to be used
(g++, etc.). If you do not require support for C++ applications,
you can disable this support using the configure option
--disable-cxx (configuring MPICH2 is described in step 1(d)
below).
- OPTIONAL: A Fortran 77 compiler, if Fortran 77 applications are
to be used (gfortran, ifort, etc.). If you do not require
support for Fortran 77 applications, you can disable this
support using --disable-f77 (configuring MPICH2 is described in
step 1(d) below).
- OPTIONAL: A Fortran 90 compiler, if Fortran 90 applications are
to be used (gfortran, ifort, etc.). If you do not require
support for Fortran 90 applications, you can disable this
support using --disable-fc. Note that Fortran 77 support is a
prerequisite for Fortran 90 support (configuring MPICH2 is
described in step 1(d) below).
Also, you need to know what shell you are using since different shell
has different command syntax. Command "echo $SHELL" prints out the
current shell used by your terminal program.
(b) Unpack the tar file and go to the top level directory:
tar xzf mpich2-1.4.1p1.tar.gz
cd mpich2-1.4.1p1
If your tar doesn't accept the z option, use
gunzip mpich2-1.4.1p1.tar.gz
tar xf mpich2-1.4.1p1.tar
cd mpich2-1.4.1p1
(c) Choose an installation directory, say
/home//mpich2-install, which is assumed to non-existent
or empty. It will be most convenient if this directory is shared
by all of the machines where you intend to run processes. If not,
you will have to duplicate it on the other machines after
installation.
(d) Configure MPICH2 specifying the installation directory:
for csh and tcsh:
./configure --prefix=/home//mpich2-install |& tee c.txt
for bash and sh:
./configure --prefix=/home//mpich2-install 2>&1 | tee c.txt
Bourne-like shells, sh and bash, accept "2>&1 |". Csh-like shell,
csh and tcsh, accept "|&". If a failure occurs, the configure
command will display the error. Most errors are straight-forward
to follow. For example, if the configure command fails with:
"No Fortran 77 compiler found. If you don't need to build any
Fortran programs, you can disable Fortran support using
--disable-f77 and --disable-fc. If you do want to build
Fortran programs, you need to install a Fortran compiler such
as gfortran or ifort before you can proceed."
... it means that you don't have a Fortran compiler :-). You will
need to either install one, or disable Fortran support in MPICH2.
If you are unable to understand what went wrong, please go to step
1(i) below, for reporting the issue to the MPICH2 developers and
other users.
(e) Build MPICH2:
for csh and tcsh:
make |& tee m.txt
for bash and sh:
make 2>&1 | tee m.txt
This step should succeed if there were no problems with the
preceding step. Check file m.txt. If there were problems, do a
"make clean" and then run make again with V=1.
make V=1 |& tee m.txt (for csh and tcsh)
OR
make V=1 2>&1 | tee m.txt (for bash and sh)
Then go to step 1(i) below, for reporting the issue to the MPICH2
developers and other users.
(f) Install the MPICH2 commands:
for csh and tcsh:
make install |& tee mi.txt
for bash and sh:
make install 2>&1 | tee mi.txt
This step collects all required executables and scripts in the bin
subdirectory of the directory specified by the prefix argument to
configure.
(g) Add the bin subdirectory of the installation directory to your
path in your startup script (.bashrc for bash, .cshrc for csh,
etc.):
for csh and tcsh:
setenv PATH /home//mpich2-install/bin:$PATH
for bash and sh:
PATH=/home//mpich2-install/bin:$PATH ; export PATH
Check that everything is in order at this point by doing:
which mpicc
which mpiexec
These commands should display the path to your bin subdirectory of
your install directory.
IMPORTANT NOTE: The install directory has to be visible at exactly
the same path on all machines you want to run your applications
on. This is typically achieved by installing MPICH2 on a shared
NFS file-system. If you do not have a shared NFS directory, you
will need to manually copy the install directory to all machines
at exactly the same location.
(h) MPICH2 uses a process manager for starting MPI applications. The
process manager provides the "mpiexec" executable, together with
other utility executables. MPICH2 comes packaged with multiple
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
directory, which you have already put in your path, as well as in
the directory mpich2-1.4.1p1/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,
you can use:
mpiexec -n ./examples/cpi
Test that you can run an 'n' process CPI job on multiple nodes:
mpiexec -f machinefile -n ./examples/cpi
The 'machinefile' is of the form:
host1
host2:2
host3:4 # Random comments
host4:1
'host1', 'host2', 'host3' and 'host4' are the hostnames of the
machines you want to run the job on. The ':2', ':4', ':1' segments
depict the number of processes you want to run on each node. If
nothing is specified, ':1' is assumed.
More details on interacting with Hydra can be found at
http://wiki.mcs.anl.gov/mpich2/index.php/Using_the_Hydra_Process_Manager
If you have completed all of the above steps, you have successfully
installed MPICH2 and run an MPI example.
(i) If you run into any errors configuring, building or running
MPICH2, please send the below files to mpich-discuss@mcs.anl.gov.
PLEASE COMPRESS BEFORE SENDING, AS THE FILES CAN BE LARGE. Note that,
depending on which step the build failed, some of the files might not
exist.
mpich2-1.4.1p1/c.txt (generated in step 1(d) above)
mpich2-1.4.1p1/m.txt (generated in step 1(e) above)
mpich2-1.4.1p1/mi.txt (generated in step 1(f) above)
mpich2-1.4.1p1/config.log (generated in step 1(d) above)
mpich2-1.4.1p1/src/openpa/config.log (generated in step 1(d) above)
More details on arguments to mpiexec are given in the User's Guide in
the doc subdirectory.
-------------------------------------------------------------------------
2. Compiler Flags
=================
MPICH2 allows several sets of compiler flags to be used. The first
three sets are configure-time options for MPICH2, while the fourth is
only relevant when compiling applications with mpicc and friends.
(a) CFLAGS, CPPFLAGS, CXXFLAGS, FFLAGS, FCFLAGS, LDFLAGS and LIBS
(abbreviated as xFLAGS): Setting these flags would result in the
MPICH2 library being compiled/linked with these flags and the flags
internally being used in mpicc and friends.
(b) MPICH2LIB_CFLAGS, MPICH2LIB_CPPFLAGS, MPICH2LIB_CXXFLAGS,
MPICH2LIB_FFLAGS, MPICH2LIB_FCFLAGS, MPICH2LIB_LDFLAGS and
MPICH2LIB_LIBS (abbreviated as MPICH2LIB_xFLAGS): Setting these flags
would result in the MPICH2 library being compiled/linked with these
flags. However, these flags will *not* be used by mpicc and friends.
(c) MPICH2_MAKE_CFLAGS: Setting these flags would result in MPICH2's
configure tests to not use these flags, but the makefile's to use
them. This is a temporary hack for certain cases that advanced
developers might be interested in, but which break existing configure
tests (e.g., -Werror). These are NOT recommended for regular users.
(d) MPICH2_MPICC_FLAGS, MPICH2_MPICPP_FLAGS, MPICH2_MPICXX_FLAGS,
MPICH2_MPIF77_FLAGS, MPICH2_MPIFC_FLAGS, MPICH2_LDFLAGS and
MPICH2_LIBS (abbreviated as MPICH2_MPIX_FLAGS): These flags do *not*
affect the compilation of the MPICH2 library itself, but will be
internally used by mpicc and friends.
+--------------------------------------------------------------------+
| | | |
| | MPICH2 library | mpicc and friends |
| | | |
+--------------------+----------------------+------------------------+
| | | |
| xFLAGS | Yes | Yes |
| | | |
+--------------------+----------------------+------------------------+
| | | |
| MPICH2LIB_xFLAGS | Yes | No |
| | | |
+--------------------+----------------------+------------------------+
| | | |
| MPICH2_MAKE_xFLAGS | Yes | No |
| | | |
+--------------------+----------------------+------------------------+
| | | |
| MPICH2_MPIX_FLAGS | No | Yes |
| | | |
+--------------------+----------------------+------------------------+
All these flags can be set as part of configure command or through
environment variables.
Default flags
--------------
By default, MPICH2 automatically adds certain compiler optimizations
to MPICH2LIB_CFLAGS. The currently used optimization level is -O2.
** IMPORTANT NOTE: Remember that this only affects the compilation of
the MPICH2 library and is not used in the wrappers (mpicc and friends)
that are used to compile your applications or other libraries.
This optimization level can be changed with the --enable-fast option
passed to configure. For example, to build an MPICH2 environment with
-O3 for all language bindings, one can simply do:
./configure --enable-fast=O3
Or to disable all compiler optimizations, one can do:
./configure --disable-fast
For more details of --enable-fast, see the output of "configure
--help".
Examples
--------
Example 1:
./configure --disable-fast MPICH2LIB_CFLAGS=-O3 MPICH2LIB_FFLAGS=-O3 \
MPICH2LIB_CXXFLAGS=-O3 MPICH2LIB_FCFLAGS=-O3
This will cause the MPICH2 libraries to be built with -O3, and -O3
will *not* be included in the mpicc and other MPI wrapper script.
Example 2:
./configure --disable-fast CFLAGS=-O3 FFLAGS=-O3 CXXFLAGS=-O3 FCFLAGS=-O3
This will cause the MPICH2 libraries to be built with -O3, and -O3
will be included in the mpicc and other MPI wrapper script.
Example 3:
There are certain compiler flags that should not be used with MPICH2's
configure, e.g. gcc's -Werror, which would confuse configure and cause
certain configure tests to fail to detect the correct system features.
To use -Werror in building MPICH2 libraries, you can pass the compiler
flags during the make step through the Makefile variable
MPICH2_MAKE_CFLAGS as follows:
make MPICH2_MAKE_CFLAGS="-Wall -Werror"
The content of MPICH2_MAKE_CFLAGS is appended to the CFLAGS in all
relevant Makefiles.
-------------------------------------------------------------------------
3. Alternate Channels and Devices
=================================
The communication mechanisms in MPICH2 are called "devices". MPICH2
supports several internal devices including ch3 (default), dcmfd (for
Blue Gene/P) and globus (for Globus), as well as many third-party
devices that are released and maintained by other institutes such as
osu_ch3 (from Ohio State University for InfiniBand and iWARP), ch_mx
(from Myricom for Myrinet MX), etc.
*************************************
ch3 device
**********
The ch3 device contains different internal communication options
called "channels". We currently support nemesis (default) and sock
channels, and experimentally provide a dllchan channel within the ch3
device.
nemesis channel
---------------
Nemesis provides communication using different networks (tcp, mx) as
well as various shared-memory optimizations. To configure MPICH2 with
nemesis, you can use the following configure option:
--with-device=ch3:nemesis
The TCP network module gets configured in by default. To specify a
different network module such as MX, you can use:
--with-device=ch3:nemesis:mx
If the MX include files and libraries are not in the normal search
paths, you can specify them with the following options:
--with-mx-include= and --with-mx-lib=
... or the if lib/ and include/ are in the same directory, you can use
the following option:
--with-mx=
If the MX libraries are shared libraries, they need to be in the
shared library search path. This can be done by adding the path to
/etc/ld.so.conf, or by setting the LD_LIBRARY_PATH variable in your
.bashrc (or .tcshrc) file. It's also possible to set the shared
library search path in the binary. If you're using gcc, you can do
this by adding
LD_LIBRARY_PATH=/path/to/lib
(and)
LDFLAGS="-Wl,-rpath -Wl,/path/to/lib"
... as arguments to configure.
By default, MX allows for only eight endpoints per node causing
ch3:nemesis:mx to give initialization errors with greater than 8
processes on the same node (this is an MX error and not an inherent
limitation in the MPICH2/Nemesis design). If needed, this can be set
to a higher number when MX is loaded. We recommend the user to contact
help@myri.com for details on how to do this.
Shared-memory optimizations are enabled by default to improve
performance for multi-processor/multi-core platforms. They can be
disabled (at the cost of performance) either by setting the
environment variable MPICH_NO_LOCAL to 1, or using the following
configure option:
--enable-nemesis-dbg-nolocal
The --with-shared-memory= configure option allows you to choose how
Nemesis allocates shared memory. The options are "auto", "sysv", and
"mmap". Using "sysv" will allocate shared memory using the System V
shmget(), shmat(), etc. functions. Using "mmap" will allocate shared
memory by creating a file (in /dev/shm if it exists, otherwise /tmp),
then mmap() the file. The default is "auto". Note that System V
shared memory has limits on the size of shared memory segments so
using this for Nemesis may limit the number of processes that can be
started on a single node.
sock channel
------------
sock is the traditional TCP sockets based communication channel. It
uses TCP/IP sockets for all communication including intra-node
communication. So, though the performance of this channel is worse
than that of nemesis, it should work on almost every platform. This
channel can be configured using the following option:
--with-device=ch3:sock
sctp channel
------------
The SCTP channel is a new channel using the Stream Control
Transmission Protocol (SCTP). This channel supports regular MPI-1
operations as well as dynamic processes and RMA from MPI-2; it
currently does not offer support for multiple threads.
Configure the sctp channel by using the following option:
--with-device=ch3:sctp
If the SCTP include files and libraries are not in the normal search
paths, you can specify them with the --with-sctp-include= and
--with-sctp-lib= options, or the --with-sctp= option if lib/ and
include/ are in the same directory.
SCTP stack specific instructions:
For FreeBSD 7 and onward, SCTP comes with CURRENT and is enabled with
the "option SCTP" in the kernel configuration file. The sctp_xxx()
calls are contained within libc so to compile ch3:sctp, make a soft-link
named libsctp.a to the target libc.a, then pass the path of the
libsctp.a soft-link to --with-sctp-lib.
For FreeBSD 6.x, kernel patches and instructions can be downloaded at
http://www.sctp.org/download.html . These kernels place libsctp and
headers in /usr, so nothing needs to be specified for --with-sctp
since /usr is often in the default search path.
For Mac OS X, the SCTP Network Kernel Extension (NKE) can be
downloaded at http://sctp.fh-muenster.de/sctp-nke.html . This places
the lib and include in /usr, so nothing needs to be specified for
--with-sctp since /usr is often in the default search path.
For Linux, SCTP comes with the default kernel from 2.4.23 and later as
a module. This module can be loaded as root using "modprobe sctp".
After this is loaded, you can verify it is loaded using "lsmod".
Once loaded, the SCTP socket lib and include files must be downloaded
and installed from http://lksctp.sourceforge.net/ . The prefix
location must then be passed into --with-sctp. This bundle is called
lksctp-tools and is available for download off their website.
For Solaris, SCTP comes with the default Solaris 1 ... ...
近期下载者:
相关文件:
收藏者: