On Mon, 21 Nov 2011, Mudassar Majeed wrote:
Thank you for your answer. Actually, I used the term UDP to show the
non-connection oriented messaging. TCP creates connection between two parties
(who
communicate) but in UDP a message can be sent to any IP/port where a
process/thread is listening
Cc: "li...@razik.name"
Sent: Monday, November 21, 2011 6:07 PM
Subject: Re: [OMPI users] UDP like messaging with MPI
MPI defines only reliable communications -- it's not quite the same thing as
UDP.
Hence, if you send something, it is guaranteed to be able to be received. UDP
may
MPI defines only reliable communications -- it's not quite the same thing as
UDP.
Hence, if you send something, it is guaranteed to be able to be received. UDP
may drop packets whenever it feels like it (e.g., when it is out of resources).
Most MPI implementations will do some form of buffer
Hi!
>I know about tnıs functıons, they special requirements like the mpi_irecv
>call should be made in every process. My processes should not look for
>messages or implicitly receive them.
I understand. But then I think your UDP comparison is wrong - whatever... :)
> But messages shuddering
I know about tnıs functıons, they special requirements like the mpi_irecv call
should be made in every process. My processes should not look for messages or
implicitly receive them. But messages shuddering go into their msg queues and
retrieved when needed. Just like udp communication.
Regards
Hello Mudassar,
I think you want an "asynchronous communication".
Therefore you could use these functions:
http://mpi.deino.net/mpi_functions/MPI_Isend.html
http://mpi.deino.net/mpi_functions/MPI_Irecv.html
http://supercomputingblog.com/mpi/mpi-tutorial-5-asynchronous-communication/
Best regard
