Gilles Gouaillardet de15b623b5 do not incrementing/decrementing the opal_progress_event_state. ... Per Ralph : "I noticed that we are incrementing and decrementing the opal_progress_event state. However, this no longer has any impact whatsoever on the RML as that is running in the independent ORTE event thread. So all this actually does is impact the MPI layer by adding an unnecessary overhead." Thanks Ralph for pointing this :-) cmr=v1.8.2:reviewer=rhc:ticket=4671 This commit was SVN r31887. The following Trac tickets were found above: Ticket 4671 --> https://svn.open-mpi.org/trac/ompi/ticket/4671		2014-05-23 05:02:31 +00:00
..
common_sm_rml.c	do not incrementing/decrementing the opal_progress_event_state.	2014-05-23 05:02:31 +00:00
common_sm_rml.h	send packed buffers instead of using iovecs in common sm rml. this commit will	2012-01-05 00:11:59 +00:00
common_sm.c	In talking about this with Jeff and Ralph, we don't actually need	2013-02-12 21:10:11 +00:00
common_sm.h	New sm BTL initialization take two. This approach is pretty simple. Instead of	2013-01-11 16:24:56 +00:00
configure.m4	this commit fixes a few things. 1. silence warning in common sm. 2. remove unneeded config code in common sm. 3. move opal_shmem_base_close to a better place in opal_finalize. 4. fix opal_path_nfs output.	2011-11-28 23:41:19 +00:00
help-mpi-common-sm.txt	send packed buffers instead of using iovecs in common sm rml. this commit will	2012-01-05 00:11:59 +00:00
Makefile.am	build: add Automake-like silent/verbose macros for "ln -s ..." operations	2014-03-28 18:24:32 +00:00