1
1
openmpi/orte
Ralph Castain 48fc339718 Create an alternative mapping method that pushes responsibility
onto the backend daemons. By default, let mpirun only pack the app_context
info and send that to the backend daemons where the mapping will
be done. This significantly reduces the computational time on mpirun as it isn't
running up/down the topology tree computing thousands of binding
locations, and it reduces the launch message to a very small number of
bytes.

When running -novm, fall back to the old way of doing things
where mpirun computes the entire map and binding, and then sends
the full info to the backend daemon.

Add a new cmd line option/mca param --fwd-mpirun-port that allows
mpirun to dynamically select a port, but then passes that back to
all the other daemons so they will use that port as a static port
for their own wireup. In this mode, we no longer "phone home" directly
to mpirun, but instead use the static port to wireup at daemon
start. We then use the routing tree to rollup the initial
launch report, and limit the number of open sockets on mpirun's node.

Update ras simulator to track the new nidmap code

Cleanup some bugs in the nidmap regex code, and enhance the error message for not enough slots to include the host on which the problem is found.

Update gadget platform file

Initialize the range count when starting a new range

Fix the no-np case in managed allocation

Ensure DVM node usage gets cleaned up after each job

Update scaling.pl script to use --fwd-mpirun-port. Pre-connect the daemon to its parent during launch while we are otherwise waiting for the daemon's children to send their "phone home" rollup messages

Signed-off-by: Ralph Castain <rhc@open-mpi.org>
2017-03-07 20:43:12 -08:00
..
bindings Expose opal_set_using_threads and improve error message on missing ompi_info. 2017-01-19 07:57:58 -05:00
etc Purge whitespace from the repo 2015-06-23 20:59:57 -07:00
include Bring the RML modifications across. This is the first step in a revamp of the ORTE messaging subsystem to support fabric-based communications during launch and wireup phases. When completed, the grpcomm and plm frameworks will each have their own "conduit" for communication - each conduit corresponds to a particular RML messaging transport. This can be the active OOB-based component, or a provider from within the RML/OFI component. Messages sent down the conduit will flow across the associated transport. 2016-10-11 16:01:02 -07:00
mca Create an alternative mapping method that pushes responsibility 2017-03-07 20:43:12 -08:00
orted Create an alternative mapping method that pushes responsibility 2017-03-07 20:43:12 -08:00
runtime Create an alternative mapping method that pushes responsibility 2017-03-07 20:43:12 -08:00
test Minor cleanups 2016-12-30 16:19:42 -08:00
tools orte-clean: fix bad username/uid usage, add orte-dvm 2017-02-28 08:00:06 -05:00
util Create an alternative mapping method that pushes responsibility 2017-03-07 20:43:12 -08:00
common_sym_whitelist.txt common syms: whitelist bison-generated common symbols 2016-01-16 03:53:14 -08:00
Doxyfile Purge whitespace from the repo 2015-06-23 20:59:57 -07:00
Makefile.am Purge whitespace from the repo 2015-06-23 20:59:57 -07:00