Ralph Castain 4853457b93 The RML posted recvs are controlled by the async progress thread when in an application process. The call to finalize and close the RML is done from the main thread, and so we need to shift the actual destruct of the posted recv list to the async thread for handling or else we encounter a race condition when accessing the posted recvs. ... Thanks to Gilles for providing the required debug info		2015-07-21 08:44:23 -07:00
..
base.h	Rework the OOB selection logic to allow a component (e.g., usock) to direct that it be the sole active component. Remove prior disqualifying code in the oob/tcp component as it was too restrictive - if usock wasn't able to run, it left apps with no way to communicate to their daemon. Have the local daemon check the global modex for the RML URI info of the local procs so it can route messages between them when tcp is the primary channel.	2015-05-08 11:15:21 -07:00
Makefile.am	Consolidate all the QOS changes into one clean commit	2015-05-06 19:48:42 -07:00
owner.txt	add owner files to opa/ompi/orte mca directories	2015-02-22 15:10:23 -07:00
rml_base_channel_handlers.c	more c99 updates	2015-06-25 10:14:13 -06:00
rml_base_contact.c	Purge whitespace from the repo	2015-06-23 20:59:57 -07:00
rml_base_frame.c	The RML posted recvs are controlled by the async progress thread when in an application process. The call to finalize and close the RML is done from the main thread, and so we need to shift the actual destruct of the posted recv list to the async thread for handling or else we encounter a race condition when accessing the posted recvs.	2015-07-21 08:44:23 -07:00
rml_base_msg_handlers.c	more c99 updates	2015-06-25 10:14:13 -06:00
rml_base_receive.c	more c99 updates	2015-06-25 10:14:13 -06:00
rml_contact.h	Purge whitespace from the repo	2015-06-23 20:59:57 -07:00