As Gilles said, we actually have four pipes open to each process (one for show_help output separately from the others he mentioned). In addition, there is a Unix domain socket connection used by PMIx.
The message_local_procs code path is stale - I need to prune things now that the PMIx integration is complete. On Tue, Jan 26, 2016 at 5:53 AM, Gilles Gouaillardet < gilles.gouaillar...@gmail.com> wrote: > iirc, there are pipes between orted and app for IOF (I/O > forwarding) (stdin, stdout and stderr) > > > On Tuesday, January 26, 2016, Gianmario Pozzi <pozzigma...@gmail.com> > wrote: > >> Thank you, Ralph. >> >> What about ORTE_DAEMON_MESSAGE_LOCAL_PROCS case into orte_comm.c? I see >> it calls orte_odls.deliver_message() and the comments say something about >> delivering to children. >> >> Furthermore I can see a socket opened between orted and the application >> while it's running, what is that for? >> >> 2016-01-19 17:40 GMT+01:00 Ralph Castain <r...@open-mpi.org>: >> >>> This is on master, yes? The only orted-children communication on the >>> master (and going forward) is via PMIx. I’ve got a branch that contains the >>> error notification support so the orted can alert the child about changes >>> such as migration, and Annu Dasari and Dave Solt are working on the error >>> response APIs to the client can request specific responses by the resource >>> manager. >>> >>> >>> On Jan 19, 2016, at 4:57 AM, Gianmario Pozzi <pozzigma...@gmail.com> >>> wrote: >>> >>> Hi everyone! >>> >>> I'm one of Federico's colleagues working on orted migration. In this >>> post (http://www.open-mpi.org/community/lists/devel/2015/10/18268.php) >>> he made a summary of all the communication channels involved in each run. >>> I need to know which framework manages communications between orted and >>> its children, so that we can forward info about migrating nodes to btl. >>> Can anybody help me? >>> >>> Thank you. >>> _______________________________________________ >>> devel mailing list >>> de...@open-mpi.org >>> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel >>> Link to this post: >>> http://www.open-mpi.org/community/lists/devel/2016/01/18491.php >>> >>> >>> >>> _______________________________________________ >>> devel mailing list >>> de...@open-mpi.org >>> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel >>> Link to this post: >>> http://www.open-mpi.org/community/lists/devel/2016/01/18492.php >>> >> >> > _______________________________________________ > devel mailing list > de...@open-mpi.org > Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel > Link to this post: > http://www.open-mpi.org/community/lists/devel/2016/01/18528.php >
