George Bosilca f06198a999 BAD grpcomm now has the ability to execute the modex offline. The MPI process ... prepare the send buffer, and post the collective order to the local daemon. It then register the callback and return fromthe modex exchange. It will only wait for this modex completion when the modex_recv is called. Meanwhile, the daemon will do the allgather. This commit was SVN r21543.		2009-06-26 20:32:31 +00:00
..
bad	BAD grpcomm now has the ability to execute the modex offline. The MPI process	2009-06-26 20:32:31 +00:00
base	Extract the modex unpacking in it's own function.	2009-06-26 20:29:54 +00:00
basic	Take the next step towards fully utilizing static ports for the daemons to eliminate the initial "phone home" to mpirun by modifying the orted termination procedure to eliminate the need for a full barrier-like operation. Instead, we add a "onesided" barrier to the grpcomm framework API that releases the orted once it has completed its own contribution to the barrier - i.e., the orteds now exit as the "ack" message rolls up towards mpirun instead of sending the "ack" directly to mpirun.	2009-05-11 14:11:44 +00:00
cnos	Take the next step towards fully utilizing static ports for the daemons to eliminate the initial "phone home" to mpirun by modifying the orted termination procedure to eliminate the need for a full barrier-like operation. Instead, we add a "onesided" barrier to the grpcomm framework API that releases the orted once it has completed its own contribution to the barrier - i.e., the orteds now exit as the "ack" message rolls up towards mpirun instead of sending the "ack" directly to mpirun.	2009-05-11 14:11:44 +00:00
hier	Take the next step towards fully utilizing static ports for the daemons to eliminate the initial "phone home" to mpirun by modifying the orted termination procedure to eliminate the need for a full barrier-like operation. Instead, we add a "onesided" barrier to the grpcomm framework API that releases the orted once it has completed its own contribution to the barrier - i.e., the orteds now exit as the "ack" message rolls up towards mpirun instead of sending the "ack" directly to mpirun.	2009-05-11 14:11:44 +00:00
configure.m4	Merge the ORTE devel branch into the main trunk. Details of what this means will be circulated separately.	2008-02-28 01:57:57 +00:00
grpcomm_types.h	Separate the gathering of collective data by jobid	2008-05-02 12:00:08 +00:00
grpcomm.h	Take the next step towards fully utilizing static ports for the daemons to eliminate the initial "phone home" to mpirun by modifying the orted termination procedure to eliminate the need for a full barrier-like operation. Instead, we add a "onesided" barrier to the grpcomm framework API that releases the orted once it has completed its own contribution to the barrier - i.e., the orteds now exit as the "ack" message rolls up towards mpirun instead of sending the "ack" directly to mpirun.	2009-05-11 14:11:44 +00:00
Makefile.am	Merge the ORTE devel branch into the main trunk. Details of what this means will be circulated separately.	2008-02-28 01:57:57 +00:00