Open MPI logo

Open MPI User's 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.

Subject: Re: [OMPI users] Asynchronous behaviour of MPI Collectives
From: George Bosilca (bosilca_at_[hidden])
Date: 2009-01-23 13:32:45

On Jan 23, 2009, at 11:24 , Eugene Loh wrote:

> Jeff Squyres wrote:
>> As you have notes, MPI_Barrier is the *only* collective operation
>> that MPI guarantees to have any synchronization properties (and
>> it's a fairly weak guarantee at that; no process will exit the
>> barrier until every process has entered the barrier -- but there's
>> no guarantee that all processes leave the barrier at the same time).
> Actually, many collectives have that property due to data-causality
> conditions. E.g., MPI_Allreduce cannot exit from any process until
> every process has finished.

MPI_Allreduce is a bad example. Depending on the algorithm, this
collective can finish on some nodes, way before the others (allreduce
might be a reduce followed by a broadcast). However, there is one
thing that will _ALWAYS_ be true, all processes have reached the
MPI_Allreduce call because they had provided their data.


> As Jeff mentions, however, exit times can be "ragged" (and
> unfortunately often are).
> _______________________________________________
> users mailing list
> users_at_[hidden]