Ralph Castain 4eb6291334 Avoid conflicts when multiple collectives are underway in ORTE by giving each grpcomm component its own RML tag and posting persistent receives. We use the signature anyway to determine which collective the received message is addressing, so there is no need to post non-persistent receives. ...

This commit was SVN r32703.

2014-09-10 17:36:16 +00:00

..

grpcomm_direct_component.c

Bring over some updates from the PMIx branch - mostly just minor cleanups. Make the direct grpcomm component no longer be the default. For now, we seem to be having problems with non-blocking fence operations, so make them not be the default under any scenario (e.g., when sm is the only btl in operation).

2014-09-06 19:19:44 +00:00

grpcomm_direct.c

Avoid conflicts when multiple collectives are underway in ORTE by giving each grpcomm component its own RML tag and posting persistent receives. We use the signature anyway to determine which collective the received message is addressing, so there is no need to post non-persistent receives.

2014-09-10 17:36:16 +00:00

grpcomm_direct.h

Per the PMIx RFC:

2014-08-21 18:56:47 +00:00

Makefile.am

Per the PMIx RFC:

2014-08-21 18:56:47 +00:00