Ralph Castain e21bfeadcd Now that the BTLs are moving down to OPAL and becoming available to ORTE, there no longer is a need/desire to push performance in the OOB/TCP component. So we don't need multiple modules driving NICs in parallel, and can drop all the complicated distribution logic. Fall back to the simplified single module model, but retain the ability to run that module in its own progress thread if so directed. ...

This should eliminate the connectivity issues that have been reported, and will make maintenance of this component much easier.

cmr=v1.8.2:reviewer=jsquyres:subject=simplify the OOB/TCP component

This commit was SVN r31956.

2014-06-06 02:24:17 +00:00

..

base

orte: fix several small memory leaks

2014-05-15 15:06:27 +00:00

tcp

Now that the BTLs are moving down to OPAL and becoming available to ORTE, there no longer is a need/desire to push performance in the OOB/TCP component. So we don't need multiple modules driving NICs in parallel, and can drop all the complicated distribution logic. Fall back to the simplified single module model, but retain the ability to run that module in its own progress thread if so directed.

2014-06-06 02:24:17 +00:00

ud

Use the correct abstraction layer name for the data dirs

2014-05-08 14:32:24 +00:00

usock

The final step of the RFC: convert the <foo>libdir and friends to fit their respective code areas, and equate them all at the top. Note that we can't entirely separate things as the opal_install_dirs framework can't handle separated locations for the various trees.

2014-05-08 02:01:35 +00:00

Makefile.am

Use the correct abstraction layer name for the data dirs

2014-05-08 14:32:24 +00:00

oob.h

Fix the newly added FT event state when compiling --with-ft

2014-03-11 13:20:08 +00:00