https://github.com/open-mpi/ompi/wiki/WeeklyTelcon_20160126
Open MPI Weekly Telcon
Dialup Info: (Do not post to public mailing list or public wiki)
Attendees
Geoff PaulsenJeff SquyresBrad BentonEdgar GabrielGeoffroy ValleeJoshua Ladd
On Jan 25, 2016, at 6:22 PM, Paul Hargrove wrote:
>
> Excellent point about the --with-foo behavior.
> If an admin knows what component name to grep for then they should
> "--with-foo" that component.
> With language bindings the spelling is "--enable-mpi-foo", but the principle
> is the same.
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
iirc, there are pipes between orted and app for IOF (I/O
forwarding) (stdin, stdout and stderr)
On Tuesday, January 26, 2016, Gianmario Pozzi 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 com
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?
