1
1
openmpi/ompi
Ralph Castain a2919174d0 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.
Multiple conduits can exist at the same time, and can even point to the same base transport. Each conduit can have its own characteristics (e.g., flow control) based on the info keys provided to the "open_conduit" call. For ease during the transition period, the "legacy" RML interfaces remain as wrappers over the new conduit-based APIs using a default conduit opened during orte_init - this default conduit is tied to the OOB framework so that current behaviors are preserved. Once the transition has been completed, a one-time cleanup will be done to update all RML calls to the new APIs and the "legacy" interfaces will be deleted.

While we are at it: Remove oob/usock component to eliminate the TMPDIR length problem - get all working, including oob_stress
2016-10-11 16:01:02 -07:00
..
attribute build: Custom libmpi(_FOO) name option in configure 2016-09-29 21:47:24 -05:00
class build: Custom libmpi(_FOO) name option in configure 2016-09-29 21:47:24 -05:00
communicator 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
contrib libompitrace: Use VERSION file to set .so version 2016-09-12 18:02:06 -04:00
datatype fortran: Correct the name of MPI_INTEGER16. 2016-08-02 22:37:58 +09:00
debuggers build: Custom libmpi(_FOO) name option in configure 2016-09-29 21:47:24 -05:00
dpm build: Custom libmpi(_FOO) name option in configure 2016-09-29 21:47:24 -05:00
errhandler ompi/errhandler: silence warnings 2016-10-06 13:20:51 +09:00
etc Purge whitespace from the repo 2015-06-23 20:59:57 -07:00
file build: Custom libmpi(_FOO) name option in configure 2016-09-29 21:47:24 -05:00
group build: Custom libmpi(_FOO) name option in configure 2016-09-29 21:47:24 -05:00
include Merge pull request #1870 from jsquyres/pr/fix-unweighted-and-weights-empty 2016-08-04 08:49:58 -07:00
info build: Custom libmpi(_FOO) name option in configure 2016-09-29 21:47:24 -05:00
mca Merge pull request #2197 from tkordenbrock/topic/master/osc-rdma.put.use.true_extent 2016-10-11 10:42:02 -06:00
message build: Custom libmpi(_FOO) name option in configure 2016-09-29 21:47:24 -05:00
mpi ompi/errhandler: silence warnings 2016-10-06 13:20:51 +09:00
mpiext build: Custom libmpi(_FOO) name option in configure 2016-09-29 21:47:24 -05:00
op build: Custom libmpi(_FOO) name option in configure 2016-09-29 21:47:24 -05:00
patterns build: Custom libmpi(_FOO) name option in configure 2016-09-29 21:47:24 -05:00
peruse build: Custom libmpi(_FOO) name option in configure 2016-09-29 21:47:24 -05:00
proc build: Custom libmpi(_FOO) name option in configure 2016-09-29 21:47:24 -05:00
request build: Custom libmpi(_FOO) name option in configure 2016-09-29 21:47:24 -05:00
runtime ompi: invokes opal_cleanup() if ompi_mpi_finalize() when possible 2016-10-08 16:58:20 +09:00
tools build: Custom libmpi_FOO name fix for wrapper compilers 2016-09-30 16:40:56 -05:00
win build: Custom libmpi(_FOO) name option in configure 2016-09-29 21:47:24 -05:00
Makefile.am build: Custom libmpi(_FOO) name option in configure 2016-09-29 21:47:24 -05:00