I suspect nobody is answering because the question makes no sense to us. You are implying that the TCP socket is outside of MPI since it isn’t tied to a communicator. If you want to setup a non-MPI communication path between two procs and monitor it separate from the MPI library, you can certainly do so - there is nothing that prevents you from doing it.
I suspect that question went similarly unanswered for the same reason. > On Jun 25, 2017, at 11:08 AM, Trevour Spencer <trevourspen...@gmail.com> > wrote: > > Dear all, > I have not yet found a solution for waiting for an event (incoming message) > to occur either on a TCP socket or on a MPI communicator. I wish I could > receive some comments from you MPI experts. > If my question was unclear, I found the same problem described on the MPICH > list two years ago: > https://lists.mpich.org/pipermail/discuss/2015-June/004049.html > <https://lists.mpich.org/pipermail/discuss/2015-June/004049.html> > He received no reply either. > > Is the question stupid for some reason, is the answer trivial, or is there no > solution to this problem? > > Cheers > Trevour > > 2017-06-20 20:15 GMT+02:00 Trevour Spencer <trevourspen...@gmail.com > <mailto:trevourspen...@gmail.com>>: > Dear all, > I am looking for a solution to receive messages either via MPI or via a TCP > socket, whichever arrives next. > > Using the select() method as described for example at > http://developerweb.net/viewtopic.php?id=2933 > <http://developerweb.net/viewtopic.php?id=2933>, I can have my code wait > until any of a given set of TCP sockets receives some data. > > Does a similar solution exist, such that the code waits until data is > available either from an MPI communicator or from a TCP socket? > > Cheers > Trevour > > > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> > Virenfrei. www.avast.com > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> > <x-msg://5/#m_-4216220911187895472_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> > _______________________________________________ > users mailing list > users@lists.open-mpi.org > https://rfd.newmexicoconsortium.org/mailman/listinfo/users
_______________________________________________ users mailing list users@lists.open-mpi.org https://rfd.newmexicoconsortium.org/mailman/listinfo/users
