Ralph Castain d6d69e2b13 Get the direct routed component to work with both TCP and USOCK OOB components. We previously had setup the direct component so it would only support direct-launched applications. Thus, all routes went direct between processes. However, if the job had been launched by mpirun, this made no sense - what you wanted instead was to have each app proc talk directly to its daemon, but have the daemons all directly connect to each other. ... So we need all the routing code for dealing with cross-job communications, lifelines, etc. The HNP will be directly connected to all daemons as they must callback at startup, and so we need to track those children correctly so we know when it is okay to terminate. We still have to support direct launch, though, as this is the only component we can use in that scenario. So if the app doesn't have daemon URI info, then it must fall back to directly connecting to everything.		2014-12-07 09:11:48 -08:00
..
configure.m4	Add unix socket component to OOB - no longer require active network for local operations. Demonstrate inter-transport crossover.	2014-02-16 20:54:12 +00:00
help-oob-usock.txt	Fix copy error in file name	2014-04-08 15:31:55 +00:00
Makefile.am	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
oob_usock_component.c	Get the direct routed component to work with both TCP and USOCK OOB components. We previously had setup the direct component so it would only support direct-launched applications. Thus, all routes went direct between processes. However, if the job had been launched by mpirun, this made no sense - what you wanted instead was to have each app proc talk directly to its daemon, but have the daemons all directly connect to each other.	2014-12-07 09:11:48 -08:00
oob_usock_component.h	Add unix socket component to OOB - no longer require active network for local operations. Demonstrate inter-transport crossover.	2014-02-16 20:54:12 +00:00
oob_usock_connection.c	Get the direct routed component to work with both TCP and USOCK OOB components. We previously had setup the direct component so it would only support direct-launched applications. Thus, all routes went direct between processes. However, if the job had been launched by mpirun, this made no sense - what you wanted instead was to have each app proc talk directly to its daemon, but have the daemons all directly connect to each other.	2014-12-07 09:11:48 -08:00
oob_usock_connection.h	We do have to track the origin of messages sent over usock as the daemon does route them back down, and we need to get the "sender" info correct. Also do a better job of dealing with simultaneous connections to avoid binding to a used socket.	2014-02-20 17:27:05 +00:00
oob_usock_hdr.h	We do have to track the origin of messages sent over usock as the daemon does route them back down, and we need to get the "sender" info correct. Also do a better job of dealing with simultaneous connections to avoid binding to a used socket.	2014-02-20 17:27:05 +00:00
oob_usock_listener.c	Re-enable the usock oob component. Ensure the TCP component promotes messages for other procs to the OOB base so that other components have a chance to send the relay. Seems to be passing MTT, so let's see how it works for others.	2014-08-30 19:33:46 +00:00
oob_usock_listener.h	Add unix socket component to OOB - no longer require active network for local operations. Demonstrate inter-transport crossover.	2014-02-16 20:54:12 +00:00
oob_usock_peer.h	Add unix socket component to OOB - no longer require active network for local operations. Demonstrate inter-transport crossover.	2014-02-16 20:54:12 +00:00
oob_usock_ping.h	Add unix socket component to OOB - no longer require active network for local operations. Demonstrate inter-transport crossover.	2014-02-16 20:54:12 +00:00
oob_usock_sendrecv.c	Get the direct routed component to work with both TCP and USOCK OOB components. We previously had setup the direct component so it would only support direct-launched applications. Thus, all routes went direct between processes. However, if the job had been launched by mpirun, this made no sense - what you wanted instead was to have each app proc talk directly to its daemon, but have the daemons all directly connect to each other.	2014-12-07 09:11:48 -08:00
oob_usock_sendrecv.h	We do have to track the origin of messages sent over usock as the daemon does route them back down, and we need to get the "sender" info correct. Also do a better job of dealing with simultaneous connections to avoid binding to a used socket.	2014-02-20 17:27:05 +00:00
oob_usock.c	Get the direct routed component to work with both TCP and USOCK OOB components. We previously had setup the direct component so it would only support direct-launched applications. Thus, all routes went direct between processes. However, if the job had been launched by mpirun, this made no sense - what you wanted instead was to have each app proc talk directly to its daemon, but have the daemons all directly connect to each other.	2014-12-07 09:11:48 -08:00
oob_usock.h	Add unix socket component to OOB - no longer require active network for local operations. Demonstrate inter-transport crossover.	2014-02-16 20:54:12 +00:00