[mpich-commits] [mpich] MPICH primary repository branch, master, updated. v3.0.4-298-g1a5210c
mysql vizuser
noreply at mpich.org
Sun Jun 9 15:47:14 CDT 2013
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "MPICH primary repository".
The branch, master has been updated
via 1a5210ceec8b5ce1d23127dc7d27db430c57cbeb (commit)
via 12998543531e010ed935ba317fa6512f420b1b14 (commit)
via 7cb7990509cdf28bc2de41cd878f447d25a12d4c (commit)
from c5b1e3796a3594e2cbf1fb9614046856c45225d1 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
http://git.mpich.org/mpich.git/commitdiff/1a5210ceec8b5ce1d23127dc7d27db430c57cbeb
commit 1a5210ceec8b5ce1d23127dc7d27db430c57cbeb
Author: Pavan Balaji <balaji at mcs.anl.gov>
Date: Sun Jun 9 14:39:01 2013 -0500
Remove environment variables section from README.
diff --git a/README.vin b/README.vin
index 17bb28e..56e783d 100644
--- a/README.vin
+++ b/README.vin
@@ -25,10 +25,9 @@ on bug fixes and new releases.
6. Alternate Configure Options
7. Testing the MPICH installation
8. Fault Tolerance
-9. Environment Variables
-10. Developer Builds
-11. Installing MPICH on windows
-12. Multiple Fortran compiler support
+9. Developer Builds
+10. Installing MPICH on windows
+11. Multiple Fortran compiler support
-------------------------------------------------------------------------
@@ -829,22 +828,8 @@ These instructions can also be found on the MPICH wiki:
-------------------------------------------------------------------------
-9. Environment Variables
-========================
-
-MPICH provides several environment variables that have different
-purposes. Most of these environment variables are listed in the
-README.envvar file. Additional variables that have not yet been
-migrated to the MPICH PARAMS format are listed below.
-
- MPICH_NAMEPUB_DIR - Allows the user to override where the publish
- and lookup information is placed for connect/accept based
- applications.
-
--------------------------------------------------------------------------
-
-10. Developer Builds
-====================
+9. Developer Builds
+===================
For MPICH developers who want to directly work on the svn, there are
a few additional steps involved (people using the release tarballs do
not have to follow these steps). Details about these steps can be
@@ -853,7 +838,7 @@ http://wiki.mpich.org/mpich/index.php/Getting_And_Building_MPICH
-------------------------------------------------------------------------
-11. Installing MPICH on Windows
+10. Installing MPICH on Windows
================================
Here are the instructions for setting up MPICH on a Windows machine:
@@ -932,7 +917,7 @@ Here are the instructions for setting up MPICH on a Windows machine:
-------------------------------------------------------------------------
-12. Multiple Fortran compiler support
+11. Multiple Fortran compiler support
=====================================
If the C compiler that is used to build MPICH libraries supports both
http://git.mpich.org/mpich.git/commitdiff/12998543531e010ed935ba317fa6512f420b1b14
commit 12998543531e010ed935ba317fa6512f420b1b14
Author: Pavan Balaji <balaji at mcs.anl.gov>
Date: Sun Jun 9 14:23:08 2013 -0500
Move MPICH_NAMEPUB_DIR to the PARAM format.
diff --git a/src/nameserv/file/file_nameserv.c b/src/nameserv/file/file_nameserv.c
index 701550c..9be8af9 100644
--- a/src/nameserv/file/file_nameserv.c
+++ b/src/nameserv/file/file_nameserv.c
@@ -57,8 +57,8 @@ int MPID_NS_Create( const MPID_Info *info_ptr, MPID_NS_Handle *handle_ptr )
(*handle_ptr)->mypid = getpid();
/* Get the dirname. Could use an info value of NAMEPUB_CONTACT */
- ret = MPL_env2str("MPICH_NAMEPUB_DIR", &dirname);
- if (!ret) {
+ dirname = MPIR_PARAM_NAMESERV_FILE_PUBDIR;
+ if (!dirname) {
/* user did not specify a directory, try using HOME */
ret = MPL_env2str("HOME", &dirname);
if (!ret) {
diff --git a/src/util/param/params.yml b/src/util/param/params.yml
index 0423eb2..968a14a 100644
--- a/src/util/param/params.yml
+++ b/src/util/param/params.yml
@@ -49,6 +49,8 @@ categories:
description : "parameters that control behavior of the ch3:nemesis channel"
- name : sockets
description : control socket parameters
+ - name : process_manager
+ description : parameters that control the client-side process manager code
parameters:
##############################################################
@@ -626,6 +628,21 @@ parameters:
# Note the netmod must implement this functionality by not
# setting the comm_ops table in any VC.
+ ##############################################################
+ # process manager parameters
+ - category : process_manager
+ name : NAMESERV_FILE_PUBDIR
+ alt-env :
+ - NAMEPUB_DIR
+ type : string
+ defaultliteral : NULL
+ class : none
+ description : >-
+ Sets the directory to use for MPI service publishing in the
+ file nameserv implementation. Allows the user to override
+ where the publish and lookup information is placed for
+ connect/accept based applications.
+
...
# Local Variables:
http://git.mpich.org/mpich.git/commitdiff/7cb7990509cdf28bc2de41cd878f447d25a12d4c
commit 7cb7990509cdf28bc2de41cd878f447d25a12d4c
Author: Pavan Balaji <balaji at mcs.anl.gov>
Date: Sun Jun 9 13:28:22 2013 -0500
Remove MPICH_ASYNC_PROGRESS from the main README.
It is now covered under the PARAMS interface and is listed with the
remaining environment variables in README.envvar. Also improve the
description of the variable in README.envvar.
diff --git a/README.vin b/README.vin
index 6910baa..17bb28e 100644
--- a/README.vin
+++ b/README.vin
@@ -833,19 +833,9 @@ These instructions can also be found on the MPICH wiki:
========================
MPICH provides several environment variables that have different
-purposes. Many of these environment variables are listed in the
-README.envvar file. Some more are listed below.
-
- MPICH_ASYNC_PROGRESS - Initiates a spare thread to provide
- asynchronous progress. This improves progress semantics for
- all MPI operations including point-to-point, collective,
- one-sided operations and I/O. Setting this variable would
- increase the thread-safety level to
- MPI_THREAD_MULTIPLE. While this improves the progress
- semantics, it might cause a small amount of performance
- overhead for regular MPI operations.
-
- ************************************
+purposes. Most of these environment variables are listed in the
+README.envvar file. Additional variables that have not yet been
+migrated to the MPICH PARAMS format are listed below.
MPICH_NAMEPUB_DIR - Allows the user to override where the publish
and lookup information is placed for connect/accept based
diff --git a/src/util/param/params.yml b/src/util/param/params.yml
index 394a7fc..0423eb2 100644
--- a/src/util/param/params.yml
+++ b/src/util/param/params.yml
@@ -359,8 +359,13 @@ parameters:
default : false
class : device
description : >-
- If set to true, MPICH will spawn an additional thread to make
- asynchronous progress on all communication operations.
+ If set to true, MPICH will initiate an additional thread to
+ make asynchronous progress on all communication operations
+ including point-to-point, collective, one-sided operations and
+ I/O. Setting this variable will automatically increase the
+ thread-safety level to MPI_THREAD_MULTIPLE. While this
+ improves the progress semantics, it might cause a small amount
+ of performance overhead for regular MPI operations.
- category : threads
name : DEFAULT_THREAD_LEVEL
-----------------------------------------------------------------------
Summary of changes:
README.vin | 39 ++++++------------------------------
src/nameserv/file/file_nameserv.c | 4 +-
src/util/param/params.yml | 26 ++++++++++++++++++++++-
3 files changed, 33 insertions(+), 36 deletions(-)
hooks/post-receive
--
MPICH primary repository
More information about the commits
mailing list