Open MPI logo

Open MPI Development Mailing List Archives

  |   Home   |   Support   |   FAQ   |  

This web mail archive is frozen.

This page is part of a frozen web archive of this mailing list.

You can still navigate around this archive, but know that no new mails have been added to it since July of 2016.

Click here to be taken to the new web archives of this list; it includes all the mails that are in this frozen archive plus all new mails that have been sent to the list since it was migrated to the new archives.

From: George Bosilca (bosilca_at_[hidden])
Date: 2007-09-18 09:44:42

The setup of a communicators include as a last stage, a collective
communication. As a result, some of the nodes can exit the collective
before the others and therefore can start sending messages using this
communicator [while some of the other nodes are still waiting for the
collective completion]. This will lead to a situation where a node
receive a message for a communicator that they are building up.

There is a bug filled in trac about this. In FT-MPI we temporary put
these messages in an internal queue, and deliver them to the right
communicator only once this communicator is completely created.


On Sep 18, 2007, at 9:06 AM, Gleb Natapov wrote:

> George,
> In the comment you are saying that "a message for a not yet
> existing
> communicator can happen". Can you explain in what situation it can
> happen?
> Thanks,
> --
> Gleb.
> _______________________________________________
> devel mailing list
> devel_at_[hidden]

  • application/pkcs7-signature attachment: smime.p7s