[mpich-discuss] In-order messages

[Thakur, Rajeev]

The standard specifies the order in which messages match, not complete. They can complete in any order.

Rajeev


From: "Larson, Jeffrey M. via discuss" <discuss at mpich.org>
Reply-To: "discuss at mpich.org" <discuss at mpich.org>
Date: Thursday, March 12, 2020 at 12:46 PM
To: "discuss at mpich.org" <discuss at mpich.org>
Cc: "Larson, Jeffrey M." <jmlarson at anl.gov>, "Navarro, John-Luke Nicolas" <jnavarro at anl.gov>, "Hudson, Stephen Tobias P" <shudson at anl.gov>
Subject: [mpich-discuss] In-order messages

Hello MPICH friends,

Consider the simple two-rank MPI scenario:

  *   Rank 1 is doing calculations and giving chunks of data to rank 0 using nonblocking sends and tag=0.
  *   When rank 1 is finished, it will send it's last data (or no data) with tag=1.
  *   Rank 0 is using probes to see when data is ready to be received. It receives with any tag, knowing when to stop receiving, or give new data when a tag=0 is received.
Is it possible that rank 0 receives a tag=1 message when there are outstanding tag=0 messages?

Looking at section 3.5 of the MPI standard lets me know that

"Messages are non-overtaking: If a sender sends two messages in succession to the same destination, and both match the same receive, then this operation cannot receive the second message if the first one is still pending."

But I'm not sure if this applies to the above case. Is anytag "the same receive"?
If rank 1 puts data in its buffer, doesn't the network have to be used to communicate that to the buffer of rank 0?
While rank 1 is putting data into its buffer in order, is it possible that a tiny tag=1 message is registered in the rank 0 buffer before a massive tag=0 message?

Thank you for your help,
Jeff
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mpich.org/pipermail/discuss/attachments/20200312/be2745d1/attachment.html>