June 2013 - commits - mailman3.cels.anl.gov

[mpich] MPICH primary repository branch, master, updated. v3.0.4-308-g6dbb07a
by noreply＠mpich.org 17 Jun '13

17 Jun '13

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 6dbb07aa774daabd4c87787d87f0ec30347c256b (commit) from 155b82af636e7f38fff0c496f89bd5da83273c71 (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/6dbb07aa774daabd4c87787d87f0ec303… commit 6dbb07aa774daabd4c87787d87f0ec30347c256b Author: Wesley Bland <wbland(a)mcs.anl.gov> Date: Mon Jun 17 08:51:40 2013 -0500 Remove Windows instructions from README.vin Closes #1886. We haven't supported Windows since 1.4.1p so its time to remove information for Windows installation from the README. Signed-off-by: Pavan Balaji <balaji(a)mcs.anl.gov> diff --git a/README.vin b/README.vin index c173cd7..9d2911d 100644 --- a/README.vin +++ b/README.vin @@ -25,8 +25,7 @@ information on bug fixes and new releases. 7. Testing the MPICH installation 8. Fault Tolerance 9. Developer Builds -10. Installing MPICH on windows -11. Multiple Fortran compiler support +10. Multiple Fortran compiler support ------------------------------------------------------------------------- @@ -844,85 +843,7 @@ http://wiki.mpich.org/mpich/index.php/Getting_And_Building_MPICH ------------------------------------------------------------------------- -10. Installing MPICH on Windows -================================ - -Here are the instructions for setting up MPICH on a Windows machine: - -(a) Install: - Microsoft Developer Studio 2003 or later - Intel Fortran 8.0 or later - cygwin - choose the dos file format option - install perl and svn - -(b) Checkout mpich: - - Bring up a command prompt. - git clone git.mpich.org:mpich - -(c) Generate *.h.in - - Bring up a cygwin bash shell. - cd mpich - ./autogen.sh - exit - -(d) Execute winconfigure.wsf - -(e) Open Developer Studio - - open mpich\mpich.sln - build the ch3sockDebug mpich solution - build the ch3sockDebug mpichs project - build the ch3sockRelease mpich solution - build the ch3sockRelease mpichs project - build the Debug mpich solution - build the Release mpich solution - build the fortDebug mpich solution - build the fortRelease mpich solution - build the gfortDebug mpich solution - build the gfortRelease mpich solution - build the sfortDebug mpich solution - build the sfortRelease mpich solution - -(f) Open a command prompt - - cd to mpich\maint - execute "makegcclibs.bat" - -(g) Open another Developer Studio instance - - open mpich\examples\examples.sln - build the Release target of the cpi project - -(h) Return to Developer Studio with the mpich solution - - set the version numbers in the Installer project - build the Installer mpich solution - -(i) Test and distribute mpich\maint\ReleaseMSI\mpich.msi - - mpich.msi can be renamed, eg mpich-1.1.msi - -(j) To install the launcher: - - Copy smpd.exe to a local directory on all the nodes. - Log on to each node as an administrator and execute "smpd.exe -install" - -(k) Compile and run an MPI application: - - Compile an mpi application. Use mpi.h from mpich\src\include\win32 - and mpi.lib in mpich\lib - - Place your executable along with the mpich dlls somewhere accessable - to all the machines. - - Execute a job by running something like: mpiexec -n 3 myapp.exe - -------------------------------------------------------------------------- - -11. Multiple Fortran compiler support +10. Multiple Fortran compiler support ===================================== If the C compiler that is used to build MPICH libraries supports both ----------------------------------------------------------------------- Summary of changes: README.vin | 83 +---------------------------------------------------------- 1 files changed, 2 insertions(+), 81 deletions(-) hooks/post-receive -- MPICH primary repository

1 0

[mpich] MPICH primary repository branch, master, updated. v3.0.4-307-g155b82a
by noreply＠mpich.org 14 Jun '13

14 Jun '13

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 155b82af636e7f38fff0c496f89bd5da83273c71 (commit) from e77cac8e420b86ac993f85acffa40d1dad3d1c7e (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/155b82af636e7f38fff0c496f89bd5da8… commit 155b82af636e7f38fff0c496f89bd5da83273c71 Author: Pavan Balaji <balaji(a)mcs.anl.gov> Date: Thu Jun 13 16:54:30 2013 -0500 Fixes #1882. Remove old mcs.anl.gov references. diff --git a/README.vin b/README.vin index a13b933..c173cd7 100644 --- a/README.vin +++ b/README.vin @@ -12,9 +12,8 @@ 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 MPICH web site, -http://www.mcs.anl.gov/research/projects/mpich, contains information -on bug fixes and new releases. +detailed. Finally, the MPICH web site, http://www.mpich.org, contains +information on bug fixes and new releases. 1. Getting Started @@ -235,15 +234,15 @@ see if the problem you are facing has a simple solution. Many common problems and their solutions are listed here. 2. If you cannot find an answer on the FAQ page, look through previous -email threads on the mpich-discuss mailing list archive -(http://lists.mcs.anl.gov/pipermail/mpich-discuss/). It is likely +email threads on the discuss(a)mpich.org mailing list archive +(https://lists.mpich.org/mailman/listinfo/discuss). It is likely someone else had a similar problem, which has already been resolved before. 3. If neither of the above steps work, please send an email to -mpich-discuss(a)mcs.anl.gov. You need to subscribe to this list -(https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss) before -sending an email. +discuss(a)mpich.org. You need to subscribe to this list +(https://lists.mpich.org/mailman/listinfo/discuss) before sending an +email. Your email should contain the following files. ONCE AGAIN, PLEASE COMPRESS BEFORE SENDING, AS THE FILES CAN BE LARGE. Note that, @@ -274,9 +273,9 @@ application or benchmark and send that along in your bug report. 4. If you have found a bug in MPICH, we request that you report it at our bug tracking system: -(https://trac.mpich.org/projects/mpich/newticket). Even if you -believe you have found a bug, we recommend you sending an email to -mpich-discuss(a)mcs.anl.gov first. +(https://trac.mpich.org/projects/mpich/newticket). Even if you believe +you have found a bug, we recommend you sending an email to +discuss(a)mpich.org first. ------------------------------------------------------------------------- @@ -860,8 +859,7 @@ Here are the instructions for setting up MPICH on a Windows machine: (b) Checkout mpich: Bring up a command prompt. - (replace "yourname" with your MCS login name): - svn co https://svn.mcs.anl.gov/repos/mpi/mpich2/trunk mpich + git clone git.mpich.org:mpich (c) Generate *.h.in ----------------------------------------------------------------------- Summary of changes: README.vin | 24 +++++++++++------------- 1 files changed, 11 insertions(+), 13 deletions(-) hooks/post-receive -- MPICH primary repository

1 0

[mpich] MPICH primary repository branch, master, updated. v3.0.4-306-ge77cac8
by noreply＠mpich.org 13 Jun '13

13 Jun '13

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 e77cac8e420b86ac993f85acffa40d1dad3d1c7e (commit) from 23d3dcd1e1313fa707529969443f08069dfe29d0 (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/e77cac8e420b86ac993f85acffa40d1da… commit e77cac8e420b86ac993f85acffa40d1dad3d1c7e Author: Qi QC Zhang <keirazhang(a)cn.ibm.com> Date: Wed Aug 8 10:11:34 2012 -0400 Add dropped code change from 'Changes in PAMId layer for AIX building' (ibm) c12fc56aee6f51af3fe92d76989094000b23ced0 Heavily updated by balaji. Signed-off-by: Rob Latham <robl(a)mcs.anl.gov> diff --git a/src/mpid/common/datatype/mpid_ext32_segment.h b/src/mpid/common/datatype/mpid_ext32_segment.h index 87997d6..97eff20 100644 --- a/src/mpid/common/datatype/mpid_ext32_segment.h +++ b/src/mpid/common/datatype/mpid_ext32_segment.h @@ -45,6 +45,12 @@ it may simply have been undetermined. This should instead use either a configure-time test (for which there are macros) or a runtime test and not use this non-portable check */ + +/* Some platforms, like AIX, use BYTE_ORDER instead of __BYTE_ORDER */ +#if defined(BYTE_ORDER) && !defined(__BYTE_ORDER) +#define __BYTE_ORDER BYTE_ORDER +#endif + #if defined(WORDS_BIGENDIAN) #define BLENDIAN 0 #elif defined(WORDS_LITTLEENDIAN) ----------------------------------------------------------------------- Summary of changes: src/mpid/common/datatype/mpid_ext32_segment.h | 6 ++++++ 1 files changed, 6 insertions(+), 0 deletions(-) hooks/post-receive -- MPICH primary repository

1 0

[mpich] MPICH primary repository branch, master, updated. v3.0.4-305-g23d3dcd
by noreply＠mpich.org 11 Jun '13

11 Jun '13

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 23d3dcd1e1313fa707529969443f08069dfe29d0 (commit) via 0e527c1357b43aff182f45c471809fe5f6a4d8cf (commit) from 18bea0dab583b63ceb513ef5b98d05c9d4e27bb2 (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/23d3dcd1e1313fa707529969443f08069… commit 23d3dcd1e1313fa707529969443f08069dfe29d0 Author: Michael Blocksome <blocksom(a)us.ibm.com> Date: Tue Jun 11 13:53:42 2013 -0500 Update README.vin with bgq configure instructions. Signed-off-by: Pavan Balaji <balaji(a)mcs.anl.gov> diff --git a/README.vin b/README.vin index 56e783d..a13b933 100644 --- a/README.vin +++ b/README.vin @@ -492,19 +492,26 @@ pamid device This is the device used on the IBM Blue Gene/Q system. The following configure options can be used: - ./configure --host=powerpc64-bgq-linux --target=powerpc64-bgq-linux --build=powerpc64-linux-gnu - --with-device=pamid:BGQ --with-file-system=bg+bglockless --enable-timer-type=device - --with-fwrapname=fmpich --with-cross=src/mpid/pamid/cross/bgq8 - --with-pm=none --enable-timing=no --disable-collchk - --disable-graphics --disable-rlog --disable-sample --disable-rpath - --with-aint-size=8 --with-assert-level=2 --enable-fast=O3 - --enable-error-messages --disable-debuginfo - --enable-thread-cs=per-object --enable-handle-allocation=tls - --enable-refcount=lock-free --disable-predefined-refcount - CC=powerpc64-bgq-linux-gcc - CXX=powerpc64-bgq-linux-g++ - F77=powerpc64-bgq-linux-gfortran - FC=powerpc64-bgq-linux-gfortran + ./configure --host=powerpc64-bgq-linux \ + --with-device=pamid:BGQ \ + --with-file-system=bg+bglockless + +The Blue Gene/Q cross compilers must either be in the $PATH, or +explicitly specified using environment variables, before configure. +For example: + + PATH=$PATH:/bgsys/drivers/ppcfloor/gnu-linux/bin + +or + + CC=/bgsys/drivers/ppcfloor/gnu-linux/bin/powerpc64-bgq-linux-gcc + CXX=... + ... + +There are several other configure options that are specific to building +on a Blue Gene/Q system. See the wiki page for more information: + + https://wiki.mpich.org/mpich/index.php/BGQ ------------------------------------------------------------------------- http://git.mpich.org/mpich.git/commitdiff/0e527c1357b43aff182f45c471809fe5f… commit 0e527c1357b43aff182f45c471809fe5f6a4d8cf Author: Pavan Balaji <balaji(a)mcs.anl.gov> Date: Mon Jun 10 16:11:07 2013 -0500 Fix tt#1505. We slow down consecutive ssh connections to the same host to avoid the ssh server falling over. This patch allows the user to control how many ssh connections we allow before throttling. diff --git a/src/pm/hydra/tools/bootstrap/external/ssh.c b/src/pm/hydra/tools/bootstrap/external/ssh.c index 1a8c98e..764618f 100644 --- a/src/pm/hydra/tools/bootstrap/external/ssh.c +++ b/src/pm/hydra/tools/bootstrap/external/ssh.c @@ -17,10 +17,13 @@ static HYD_status create_element(char *hostname, struct HYDT_bscd_ssh_time **e) struct HYDT_bscd_ssh_time *tmp; HYD_status status = HYD_SUCCESS; + /* FIXME: These are never getting freed */ HYDU_MALLOC((*e), struct HYDT_bscd_ssh_time *, sizeof(struct HYDT_bscd_ssh_time), status); + HYDU_MALLOC((*e)->init_time, struct timeval *, + HYDT_bscd_ssh_limit_time * sizeof(struct timeval), status); (*e)->hostname = HYDU_strdup(hostname); - for (i = 0; i < SSH_LIMIT; i++) { + for (i = 0; i < HYDT_bscd_ssh_limit; i++) { (*e)->init_time[i].tv_sec = 0; (*e)->init_time[i].tv_usec = 0; } @@ -57,7 +60,7 @@ HYD_status HYDTI_bscd_ssh_store_launch_time(char *hostname) } /* Search for an unset element to store the current time */ - for (i = 0; i < SSH_LIMIT; i++) { + for (i = 0; i < HYDT_bscd_ssh_limit; i++) { if (e->init_time[i].tv_sec == 0 && e->init_time[i].tv_usec == 0) { gettimeofday(&e->init_time[i], NULL); goto fn_exit; @@ -67,12 +70,12 @@ HYD_status HYDTI_bscd_ssh_store_launch_time(char *hostname) /* No free element found; wait for the oldest element to turn * older */ oldest = 0; - for (i = 0; i < SSH_LIMIT; i++) + for (i = 0; i < HYDT_bscd_ssh_limit; i++) if (older(e->init_time[i], e->init_time[oldest])) oldest = i; gettimeofday(&now, NULL); - time_left = SSH_LIMIT_TIME - now.tv_sec + e->init_time[oldest].tv_sec; + time_left = HYDT_bscd_ssh_limit_time - now.tv_sec + e->init_time[oldest].tv_sec; /* A better approach will be to make progress here, but that would * mean that we need to deal with nested calls to the demux engine diff --git a/src/pm/hydra/tools/bootstrap/external/ssh.h b/src/pm/hydra/tools/bootstrap/external/ssh.h index 5197093..5bac875 100644 --- a/src/pm/hydra/tools/bootstrap/external/ssh.h +++ b/src/pm/hydra/tools/bootstrap/external/ssh.h @@ -13,8 +13,8 @@ * connections from the same IP address per minute. If we exceed that, * the server assumes it's a hack-in attack, and does not accept any * more connections. So, we limit the number of ssh connections. */ -#define SSH_LIMIT 8 -#define SSH_LIMIT_TIME 15 +#define HYDRA_LAUNCHER_SSH_DEFAULT_LIMIT 8 +#define HYDRA_LAUNCHER_SSH_DEFAULT_LIMIT_TIME 15 #define older(a,b) \ ((((a).tv_sec < (b).tv_sec) || \ @@ -22,10 +22,12 @@ struct HYDT_bscd_ssh_time { char *hostname; - struct timeval init_time[SSH_LIMIT]; + struct timeval *init_time; struct HYDT_bscd_ssh_time *next; }; +extern int HYDT_bscd_ssh_limit; +extern int HYDT_bscd_ssh_limit_time; extern struct HYDT_bscd_ssh_time *HYDT_bscd_ssh_time; HYD_status HYDTI_bscd_ssh_store_launch_time(char *hostname); diff --git a/src/pm/hydra/tools/bootstrap/external/ssh_init.c b/src/pm/hydra/tools/bootstrap/external/ssh_init.c index 4a134bb..8633b32 100644 --- a/src/pm/hydra/tools/bootstrap/external/ssh_init.c +++ b/src/pm/hydra/tools/bootstrap/external/ssh_init.c @@ -8,11 +8,24 @@ #include "bsci.h" #include "common.h" +int HYDT_bscd_ssh_limit; +int HYDT_bscd_ssh_limit_time; + HYD_status HYDT_bsci_launcher_ssh_init(void) { + int rc; + HYDT_bsci_fns.query_env_inherit = HYDT_bscd_ssh_query_env_inherit; HYDT_bsci_fns.launch_procs = HYDT_bscd_common_launch_procs; HYDT_bsci_fns.launcher_finalize = HYDT_bscd_ssh_launcher_finalize; + rc = MPL_env2int("HYDRA_LAUNCHER_SSH_LIMIT", &HYDT_bscd_ssh_limit); + if (rc == 0) + HYDT_bscd_ssh_limit = HYDRA_LAUNCHER_SSH_DEFAULT_LIMIT; + + rc = MPL_env2int("HYDRA_LAUNCHER_SSH_LIMIT_TIME", &HYDT_bscd_ssh_limit_time); + if (rc == 0) + HYDT_bscd_ssh_limit_time = HYDRA_LAUNCHER_SSH_DEFAULT_LIMIT_TIME; + return HYD_SUCCESS; } ----------------------------------------------------------------------- Summary of changes: README.vin | 33 +++++++++++++-------- src/pm/hydra/tools/bootstrap/external/ssh.c | 11 ++++-- src/pm/hydra/tools/bootstrap/external/ssh.h | 8 +++-- src/pm/hydra/tools/bootstrap/external/ssh_init.c | 13 ++++++++ 4 files changed, 45 insertions(+), 20 deletions(-) hooks/post-receive -- MPICH primary repository

1 0

[mpich] MPICH primary repository branch, master, updated. v3.0.4-303-g18bea0d
by noreply＠mpich.org 11 Jun '13

11 Jun '13

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 18bea0dab583b63ceb513ef5b98d05c9d4e27bb2 (commit) from 1199e48387de78086f2c4037dad3ea1aac156174 (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/18bea0dab583b63ceb513ef5b98d05c9d… commit 18bea0dab583b63ceb513ef5b98d05c9d4e27bb2 Author: Pavan Balaji <balaji(a)mcs.anl.gov> Date: Mon Jun 10 11:59:50 2013 -0500 Improved timer-type detection. If the device specified a timer type, use that by default. If none is specified, configure will try to detect one. User-specified types are always given priority. Signed-off-by: Michael Blocksome <blocksom(a)us.ibm.com> diff --git a/configure.ac b/configure.ac index 39c20a6..21f174e 100644 --- a/configure.ac +++ b/configure.ac @@ -4784,6 +4784,14 @@ fi MPID_TIMER_TYPE=long AC_SUBST(MPID_TIMER_TYPE) +# If the device specified a timer type, use that by default. Else, +# try to detect a type that works on this system. +if test -n "$MPID_DEVICE_TIMER_TYPE" ; then + default_timer_type=device +else + default_timer_type= +fi + # clock_gettime is the POSIX gettimeofday # gethrtime is the Solaris high-resolution timer dnl @@ -4819,7 +4827,7 @@ AC_ARG_ENABLE(timer-type, certain situations. linuxalpha_cycle is no longer supported. -],timer_type=$enable_timer_type) +],timer_type=$enable_timer_type,timer_type=${default_timer_type}) if test -z "$timer_type" ; then # Try to pick a timer based on what is available ----------------------------------------------------------------------- Summary of changes: configure.ac | 10 +++++++++- 1 files changed, 9 insertions(+), 1 deletions(-) hooks/post-receive -- MPICH primary repository

1 0

[mpich] MPICH primary repository branch, master, updated. v3.0.4-302-g1199e48
by noreply＠mpich.org 11 Jun '13

11 Jun '13

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 1199e48387de78086f2c4037dad3ea1aac156174 (commit) via cc5bafd7e2c5bc6fd6162d2c77f31d462066d785 (commit) from 40e4efb73d8b88f8a47ea38f95cd67c1df96c700 (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/1199e48387de78086f2c4037dad3ea1aa… commit 1199e48387de78086f2c4037dad3ea1aac156174 Author: Michael Blocksome <blocksom(a)us.ibm.com> Date: Tue Jun 11 12:05:55 2013 -0500 pamid bgq fix for spi includes This will match the #include usage in the `hwloc` package. Signed-off-by: Bob Cernohous <bobc(a)us.ibm.com> diff --git a/src/mpid/pamid/include/mpidi_mutex.h b/src/mpid/pamid/include/mpidi_mutex.h index 052834c..d757ecb 100644 --- a/src/mpid/pamid/include/mpidi_mutex.h +++ b/src/mpid/pamid/include/mpidi_mutex.h @@ -38,9 +38,9 @@ #define MUTEX_FAIL 0x8000000000000000UL -#include "kernel/location.h" -#include "kernel/memory.h" -#include "l2/atomic.h" +#include <spi/include/kernel/location.h> +#include <spi/include/kernel/memory.h> +#include <spi/include/l2/atomic.h> #define MPIDI_MAX_MUTEXES 16 @@ -159,7 +159,7 @@ MPIDI_Mutex_release(unsigned m) -#include <kernel/location.h> +#include <spi/include/kernel/location.h> #define MPIDI_MAX_MUTEXES 16 typedef OPA_int_t MPIDI_Mutex_t; diff --git a/src/mpid/pamid/subconfigure.m4 b/src/mpid/pamid/subconfigure.m4 index 298ed9d..880040e 100644 --- a/src/mpid/pamid/subconfigure.m4 +++ b/src/mpid/pamid/subconfigure.m4 @@ -125,7 +125,6 @@ if test "${pamid_platform}" = "BGQ" ; then if test -d ${bgq_driver}/spi/include ; then PAC_APPEND_FLAG([-I${bgq_driver}], [CPPFLAGS]) - PAC_APPEND_FLAG([-I${bgq_driver}/spi/include], [CPPFLAGS]) PAC_APPEND_FLAG([-I${bgq_driver}/spi/include/kernel/cnk], [CPPFLAGS]) PAC_APPEND_FLAG([-I${bgq_driver}], [WRAPPER_CFLAGS]) http://git.mpich.org/mpich.git/commitdiff/cc5bafd7e2c5bc6fd6162d2c77f31d462… commit cc5bafd7e2c5bc6fd6162d2c77f31d462066d785 Author: Michael Blocksome <blocksom(a)us.ibm.com> Date: Tue Jun 11 10:38:12 2013 -0500 Check for the 'comm/sys' directory before adding to compiler flags Signed-off-by: Bob Cernohous <bobc(a)us.ibm.com> diff --git a/src/mpid/pamid/subconfigure.m4 b/src/mpid/pamid/subconfigure.m4 index 1b5171c..298ed9d 100644 --- a/src/mpid/pamid/subconfigure.m4 +++ b/src/mpid/pamid/subconfigure.m4 @@ -125,7 +125,6 @@ if test "${pamid_platform}" = "BGQ" ; then if test -d ${bgq_driver}/spi/include ; then PAC_APPEND_FLAG([-I${bgq_driver}], [CPPFLAGS]) - PAC_APPEND_FLAG([-I${bgq_driver}/comm/sys/include], [CPPFLAGS]) PAC_APPEND_FLAG([-I${bgq_driver}/spi/include], [CPPFLAGS]) PAC_APPEND_FLAG([-I${bgq_driver}/spi/include/kernel/cnk], [CPPFLAGS]) @@ -134,15 +133,21 @@ if test "${pamid_platform}" = "BGQ" ; then PAC_APPEND_FLAG([-I${bgq_driver}], [WRAPPER_FCFLAGS]) PAC_APPEND_FLAG([-I${bgq_driver}], [WRAPPER_FFLAGS]) - PAC_APPEND_FLAG([-I${bgq_driver}/comm/sys/include], [WRAPPER_CFLAGS]) - PAC_APPEND_FLAG([-I${bgq_driver}/comm/sys/include], [WRAPPER_CXXFLAGS]) - PAC_APPEND_FLAG([-I${bgq_driver}/comm/sys/include], [WRAPPER_FCFLAGS]) - PAC_APPEND_FLAG([-I${bgq_driver}/comm/sys/include], [WRAPPER_FFLAGS]) + if test -d {bgq_driver}/comm/include ; then + PAC_APPEND_FLAG([-I${bgq_driver}/comm/include], [CPPFLAGS]) - PAC_APPEND_FLAG([-I${bgq_driver}/spi/include], [WRAPPER_CFLAGS]) - PAC_APPEND_FLAG([-I${bgq_driver}/spi/include], [WRAPPER_CXXFLAGS]) - PAC_APPEND_FLAG([-I${bgq_driver}/spi/include], [WRAPPER_FCFLAGS]) - PAC_APPEND_FLAG([-I${bgq_driver}/spi/include], [WRAPPER_FFLAGS]) + PAC_APPEND_FLAG([-I${bgq_driver}/comm/include], [WRAPPER_CFLAGS]) + PAC_APPEND_FLAG([-I${bgq_driver}/comm/include], [WRAPPER_CXXFLAGS]) + PAC_APPEND_FLAG([-I${bgq_driver}/comm/include], [WRAPPER_FCFLAGS]) + PAC_APPEND_FLAG([-I${bgq_driver}/comm/include], [WRAPPER_FFLAGS]) + else + PAC_APPEND_FLAG([-I${bgq_driver}/comm/sys/include], [CPPFLAGS]) + + PAC_APPEND_FLAG([-I${bgq_driver}/comm/sys/include], [WRAPPER_CFLAGS]) + PAC_APPEND_FLAG([-I${bgq_driver}/comm/sys/include], [WRAPPER_CXXFLAGS]) + PAC_APPEND_FLAG([-I${bgq_driver}/comm/sys/include], [WRAPPER_FCFLAGS]) + PAC_APPEND_FLAG([-I${bgq_driver}/comm/sys/include], [WRAPPER_FFLAGS]) + fi PAC_APPEND_FLAG([-I${bgq_driver}/spi/include/kernel/cnk], [WRAPPER_CFLAGS]) PAC_APPEND_FLAG([-I${bgq_driver}/spi/include/kernel/cnk], [WRAPPER_CXXFLAGS]) @@ -152,10 +157,11 @@ if test "${pamid_platform}" = "BGQ" ; then PAC_APPEND_FLAG([-L${bgq_driver}/spi/lib], [LDFLAGS]) PAC_APPEND_FLAG([-L${bgq_driver}/spi/lib], [WRAPPER_LDFLAGS]) - PAC_APPEND_FLAG([-L${bgq_driver}/comm/sys/lib], [WRAPPER_LDFLAGS]) - - PAC_APPEND_FLAG([-L${bgq_driver}/spi/lib], [WRAPPER_LDFLAGS]) - PAC_APPEND_FLAG([-L${bgq_driver}/comm/sys/lib], [WRAPPER_LDFLAGS]) + if test -d ${bgq_driver}/comm/sys/lib ; then + PAC_APPEND_FLAG([-L${bgq_driver}/comm/sys/lib], [WRAPPER_LDFLAGS]) + else + PAC_APPEND_FLAG([-L${bgq_driver}/comm/lib], [WRAPPER_LDFLAGS]) + fi break fi ----------------------------------------------------------------------- Summary of changes: src/mpid/pamid/include/mpidi_mutex.h | 8 ++++---- src/mpid/pamid/subconfigure.m4 | 33 +++++++++++++++++++-------------- 2 files changed, 23 insertions(+), 18 deletions(-) hooks/post-receive -- MPICH primary repository

1 0

[mpich] MPICH primary repository branch, master, updated. v3.0.4-300-g40e4efb
by noreply＠mpich.org 10 Jun '13

10 Jun '13

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 40e4efb73d8b88f8a47ea38f95cd67c1df96c700 (commit) from c2417a7c15e7eef43d74bbef1ccc3d0915155cd8 (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/40e4efb73d8b88f8a47ea38f95cd67c1d… commit 40e4efb73d8b88f8a47ea38f95cd67c1df96c700 Author: Pavan Balaji <balaji(a)mcs.anl.gov> Date: Mon Jun 10 07:14:27 2013 -0500 Revert [6a4899dc]. The previous patch was meant to allow devices to automatically pick the default timer type they like. However, it forces the device to pick one of the predefined timer types. diff --git a/configure.ac b/configure.ac index 6c20767..39c20a6 100644 --- a/configure.ac +++ b/configure.ac @@ -4819,7 +4819,7 @@ AC_ARG_ENABLE(timer-type, certain situations. linuxalpha_cycle is no longer supported. -],timer_type=$enable_timer_type,timer_type=$MPID_DEFAULT_TIMER_TYPE) +],timer_type=$enable_timer_type) if test -z "$timer_type" ; then # Try to pick a timer based on what is available @@ -5062,6 +5062,14 @@ pac_cv_ia64_cycle,[ MPID_TIMER_TYPE="uint64_t" ;; + device) + # The device selected should export the datatype for the timer + # in MPID_DEVICE_TIMER_TYPE if something other than long is needed + if test -n "$MPID_DEVICE_TIMER_TYPE" ; then + MPID_TIMER_TYPE=$MPID_DEVICE_TIMER_TYPE + fi + ;; + *) AC_MSG_ERROR([Invalid timer type $timer_type]) ;; ----------------------------------------------------------------------- Summary of changes: configure.ac | 10 +++++++++- 1 files changed, 9 insertions(+), 1 deletions(-) hooks/post-receive -- MPICH primary repository

1 0

[mpich] MPICH primary repository branch, master, updated. v3.0.4-299-gc2417a7
by noreply＠mpich.org 09 Jun '13

09 Jun '13

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 c2417a7c15e7eef43d74bbef1ccc3d0915155cd8 (commit) from 1a5210ceec8b5ce1d23127dc7d27db430c57cbeb (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/c2417a7c15e7eef43d74bbef1ccc3d091… commit c2417a7c15e7eef43d74bbef1ccc3d0915155cd8 Author: Pavan Balaji <balaji(a)mcs.anl.gov> Date: Sun Jun 9 21:02:56 2013 -0500 Improved README text for ASYNC_PROGRESS. diff --git a/src/util/param/params.yml b/src/util/param/params.yml index 968a14a..d5f4300 100644 --- a/src/util/param/params.yml +++ b/src/util/param/params.yml @@ -367,7 +367,12 @@ parameters: 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. + of performance overhead for regular MPI operations. The user + is encouraged to leave one or more hardware threads vacant in + order to prevent contention between the application threads + and the progress thread(s). The impact of oversubscription is + highly system dependent but may be substantial in some cases, + hence this recommendation. - category : threads name : DEFAULT_THREAD_LEVEL ----------------------------------------------------------------------- Summary of changes: src/util/param/params.yml | 7 ++++++- 1 files changed, 6 insertions(+), 1 deletions(-) hooks/post-receive -- MPICH primary repository

1 0

[mpich] MPICH primary repository branch, master, updated. v3.0.4-298-g1a5210c
by noreply＠mpich.org 09 Jun '13

09 Jun '13

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/1a5210ceec8b5ce1d23127dc7d27db430… commit 1a5210ceec8b5ce1d23127dc7d27db430c57cbeb Author: Pavan Balaji <balaji(a)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/12998543531e010ed935ba317fa6512f4… commit 12998543531e010ed935ba317fa6512f420b1b14 Author: Pavan Balaji <balaji(a)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/7cb7990509cdf28bc2de41cd878f447d2… commit 7cb7990509cdf28bc2de41cd878f447d25a12d4c Author: Pavan Balaji <balaji(a)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

1 0

[mpich] MPICH primary repository branch, master, updated. v3.0.4-295-gc5b1e37
by noreply＠mpich.org 09 Jun '13

09 Jun '13

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 c5b1e3796a3594e2cbf1fb9614046856c45225d1 (commit) from a5719ca872c316e5d4545acf7e2be0eaad5e7d92 (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/c5b1e3796a3594e2cbf1fb9614046856c… commit c5b1e3796a3594e2cbf1fb9614046856c45225d1 Author: Pavan Balaji <balaji(a)mcs.anl.gov> Date: Sun Jun 9 11:12:28 2013 -0500 Place the preferred environment variable name at the top. MPIR_PARAM_ gets higher priority than MPICH_. So we place the MPIR_PARAM_ version as the preferred environment variable name, but provide the MPICH_ version as an alternative. diff --git a/maint/genparams b/maint/genparams index 94c575d..36bbad0 100755 --- a/maint/genparams +++ b/maint/genparams @@ -465,12 +465,12 @@ foreach my $p (@{$params->{parameters}}) { my $default; # process extra envs first so the primary always wins - push @env_names, map { "${alt_ns}_$_" } @{$p->{'alt-env'}}; - push @env_names, "${uc_ns}_" . $p->{name}; + push @env_names, "${alt_ns}_" . $p->{name}; push @env_names, map { "${uc_ns}_$_" } @{$p->{'alt-env'}}; + push @env_names, map { "${alt_ns}_$_" } @{$p->{'alt-env'}}; push @env_names, @{$p->{'abs-alt-env'}} if $p->{'abs-alt-env'}; - print PARAM_README "${alt_ns}_$p->{name}\n"; + print PARAM_README "${uc_ns}_$p->{name}\n"; $first = 1; foreach $alt (@env_names) { ----------------------------------------------------------------------- Summary of changes: maint/genparams | 6 +++--- 1 files changed, 3 insertions(+), 3 deletions(-) hooks/post-receive -- MPICH primary repository

1 0