0404444dbe
- mca_base_param_file_prefix
(Default: NULL)
This is the fullname of the "-am" mpirun option. Used to specify a ':'
separated list of AMCA parameter set files.
- mca_base_param_file_path
(Default: $SYSCONFDIR/amca-param-sets/:$CWD)
The path to search for AMCA files with relative paths. A warning will be
printed if the AMCA file cannot be found.
* Added a new function "mca_base_param_recache_files" the re-reads the file
configurations. This is used internally to help bootstrap the MCA system.
* Added a new orterun/mpirun command line option '-am' that aliases for the
mca_base_param_file_prefix MCA parameter
* Exposed the opal_path_access function as it is generally useful in other
places in the code.
* New function "opal_cmd_line_make_opt_mca" which will allow you to append a
new command line option with MCA parameter identifiers to set at the same
time. Previously this could only be done at command line declaration time.
* Added a new directory under the $pkgdatadir named "amca-param-sets" where all
the 'shipped with' Open MPI AMCA parameter sets are placed. This is the first
place to search for AMCA sets with relative paths.
* An example.conf AMCA parameter set file is located in
contrib/amca-param-sets/.
* Jeff Squyres contributed an OpenIB AMCA set for benchmarking.
Note: You will need to autogen with this commit as it adds a configure param.
Sorry :(
This commit was SVN r13867.
20 строки
622 B
Plaintext
20 строки
622 B
Plaintext
#
|
|
# These values are suitable for benchmarking with the openib and sm
|
|
# btls with a small number of MPI processes. If you're only going to
|
|
# use one process per node, remove "sm". These values are *NOT*
|
|
# scalable to large numbers of processes!
|
|
#
|
|
btl=openib,self,sm
|
|
btl_openib_max_btls=20
|
|
btl_openib_rd_num=128
|
|
btl_openib_rd_low=75
|
|
btl_openib_rd_win=50
|
|
btl_openib_max_eager_rdma=32
|
|
mpool_base_use_mem_hooks=1
|
|
mpi_leave_pinned=1
|
|
#
|
|
# Note that we are not limiting the max free list size, so for netpipe
|
|
# (for example), this is no problem. But we may want to explore the
|
|
# parameter space for other popular benchmarks.
|
|
#
|