[Mpi-forum] Question about the semantics of MPI_Comm_disconnect
Anh.Vo at microsoft.com
Tue Nov 12 13:24:59 CST 2013
I think matched implies complete, but not necessary the opposite. On the sender side a send might be complete, but we don't know if it has been matched yet.
But I agree the wording is confusing, it should say "or matched".
From: mpi-forum [mailto:mpi-forum-bounces at lists.mpi-forum.org] On Behalf Of Jeff Squyres (jsquyres)
Sent: Tuesday, November 12, 2013 11:09 AM
To: Main MPI Forum mailing list
Subject: Re: [Mpi-forum] Question about the semantics of MPI_Comm_disconnect
On Nov 12, 2013, at 2:02 PM, Nathan Hjelm <hjelmn at lanl.gov> wrote:
> I am trying to understand the semantics of MPI_Comm_disconnect but there is a contradiction in the standard. On page 400, lines 29-31 the standard states:
> MPI_COMM_DISCONNECT may be called only if all communication is
> complete and matched, so that buffered data can be delivered to its destination. This requirement is the same as for MPI_FINALIZE.
I'm also curious about the phrase "complete and matched" -- does anyone know why it says "and matched"? I would think that "complete" directly implies "matched". ...or did it mean to say "...or matched" (vs. "...and matched")?
> Which suggests that all communication MUST be complete before MPI_Comm_disconnect is called. But if I look at lines 41-43 I see this:
> Rationale. It would be nice to be able to use MPI_COMM_FREE instead,
> but that function explicitly does not wait for pending communication
> to complete. (End of
Also, some normative text on line 32 says:
MPI_COMM_DISCONNECT has the same action as MPI_COMM_FREE, except that it waits for pending communication to finish internally...
Which seems to directly contradict the statement starting on line 28.
jsquyres at cisco.com
For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
mpi-forum mailing list
mpi-forum at lists.mpi-forum.org
More information about the mpi-forum