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.

Subject: Re: [OMPI devel] collective problems
From: Andrew Friedley (afriedle_at_[hidden])
Date: 2007-11-08 11:09:06

Brian Barrett wrote:
> Personally, I'd rather just not mark MPI completion until a local
> completion callback from the BTL. But others don't like that idea, so
> we came up with a way for back pressure from the BTL to say "it's not
> on the wire yet". This is more complicated than just not marking MPI
> completion early, but why would we do something that helps real apps
> at the expense of benchmarks? That would just be silly!

FWIW this issue is also very relevant for the UD BTL, especially with
some new work I've done in the last week (currently having problems with
send-side completion semantics). I missed it, what was the reasoning
for not marking MPI completion until a callback from the BTL?