Ralph Castain e884cbf5f5 Even though the ofi component doesn't do any routing itself, the rest of the code base (e.g., grpcomm) needs to know what routing module this component is using. So set it to the "direct" module, and don't allow ofi to be used if that module isn't available. ...

Signed-off-by: Ralph Castain <rhc@open-mpi.org>

2017-06-02 15:47:25 -07:00

..

.opal_ignore

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

.opal_unignore

Add CPPFLAGS to build of rml/ofi component.

2017-02-25 09:17:41 -08:00

configure.m4

common/libfabric: move libfabric to ofi

2017-04-20 13:07:16 -06:00

Makefile.am

common/libfabric: move libfabric to ofi

2017-04-20 13:07:16 -06:00

rml_ofi_component.c

Even though the ofi component doesn't do any routing itself, the rest of the code base (e.g., grpcomm) needs to know what routing module this component is using. So set it to the "direct" module, and don't allow ofi to be used if that module isn't available.

2017-06-02 15:47:25 -07:00

rml_ofi_request.h

Adding ofi plugin to allow for opening a conduit to use ethernet/fabric.

2016-10-26 13:11:07 -07:00

rml_ofi_send.c

Cleaned up the send_msg(), moved checking for send to self into the send_nb()

2017-06-01 17:50:54 -07:00

rml_ofi.h

Adding ofi plugin to allow for opening a conduit to use ethernet/fabric.

2016-10-26 13:11:07 -07:00