- mca_base_param_set_int() -- set the value of an MCA int param from
the API
- mca_base_param_set_string() -- set the value of an MCA string param
from the API
- mca_base_param_unsed() -- unset a previously set MCA param (string
or int)
- mca_base_param_dump() -- obtain a listing of all currently
registered MCA params
- mca_base_param_dump_release() -- release the list of all registered
MCA params that was obtained from mca_base_param_dump()
See Doxygen docs in src/mca/base/mca_base_param.h for details of these
functions.
This commit was SVN r4415.
parameters. These are intended to be used by the system itself for
passing information around, and are not generally intended for the
user to see or modify. Hence, we flag them as "internal" which causes
them not to show up in the ompi_info output (by default). This
"security through obscurity" is good enough -- it's really only
intended to keep casual observers away. The MCA parameters are still
there and are still settable (if a developer wants to set them).
To mark an MCA parameter as internal, simply call
mca_param_set_internal() with its index. I debated about adding a
flag to mca_param_register_[int|string](), but then would have
involved changing a *lot* of code throughout the base -- and internal
MCA parameters is certainly not the common case.
Note that you can provide the new ompi_info flag --internal in
conjunction with the --param flag to force it to also show all the
internal MCA params.
This commit was SVN r4373.
Ensure that OMPI_F77_* are always defined, even if a) a f77 compiler
is not found, or b) the user disables the f77 MPI bindings.
This commit was SVN r2618.
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.
