per-host / per-config basis because some people (like me!) have a
common scratch root on NFS for multiple machines (e.g., share a
downloads directory).
This commit was SVN r2410.
resolution is now (effectively):
- read from MPI keyval (if associated)
- read from command line
- read from environment
- read from file
More capabilities will be added shortly for developers to
programatically set MCA parameter values
- Create [empty but commented] system-wide MCA param file that gets
installed at $sysconf/openmpi-mca-params.conf (i.e.,
$prefix/etc/openmpi-mca-params.conf)
- The following files are opened and read (in order):
1. $sysconf/openmpi-mca-params.conf
2. $HOME/.openmpi/mca-params.conf
Specifically, the values in 2) will override the values in 1) (so
users can override system-wide defaults.
- Update MCA string params to allow for "~/" in the middle to be
expanded to the user's home directory.
- Added to default value of MCA parameter component_path to be:
$pkglibdir:$HOME/.openmpi/components
$pkglibdir is typically $prefix/lib/openmpi. So now both of these
directories will be searched for components at run time (in all Open
MPI executables, including ompi_info). Note that this is an MCA
parameter, so it, too, can be changed at run-time.
- Updated all docs to match this behavior -- some is \internal, so it
doesn't show unless you tell doxygen to generate internal docs
(which is not the default)
- update ompi_info to handle new behavior; ompi_info --param now shows
the *current* default value (i.e., it will look in the environment
and/or files to find out what the default values are -- so if you
change a value in $HOME/.openmpi/mca-params.conf, it should be
reflected in "ompi_info --param all all")
- updated bunches of doxygen docs to match
- this diff is slightly artifically large -- some of the changes are
converstions to 4 space tabs (I re-indented my own code that
previously used 2 space tabs)
This commit was SVN r2408.
- ensure to only keep a finite number of old build roots around (build
roots are kept if you --leave-install or if there was a build error
-- so you can go look and see what the error was, etc.)
- check to see if the last run already built the same tarball version
that's currently on the nightly build website -- if we've already
tested it, there's no point in compiling / testing it again. This
should cut down on the volume of [repetitive] testing e-mails to the
mailing list.
- add --force parameter to override ^^ -- *always* compile/test,
regardless of whether we have tested that version before.
- fix logic removing old tarballs
This commit was SVN r2405.
a pointer to the fragment.
-- Done with shared send completion queue support
-- To test thead-based send/recv completion checking
Points to be aware,
i) Expand control mesg header type and Optimize completion checking.
ii) Introduce additional control message for management functionality.
This commit was SVN r2389.
BTW, in case anyone is trying to use threads, be aware that much of the RTE is NOT thread-safe at this time. We'll work on that soon.
:-)
This commit was SVN r2379.
