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] RFC: eliminating "descriptor" argument from sendi function
From: Brian W. Barrett (brbarret_at_[hidden])
Date: 2009-02-23 11:24:12

At a high level, it seems reasonable to me. I am not familiar enough with
the sendi code, however, to have a strong opinion either way.


On Mon, 23 Feb 2009, Jeff Squyres wrote:

> Sounds reasonable to me. George / Brian?
> On Feb 21, 2009, at 2:11 AM, Eugene Loh wrote:
>> What: Eliminate the "descriptor" argument from sendi functions.
>> Why: The only thing this argument is used for is so that the sendi
>> function can allocate a descriptor in the event that the "send" cannot
>> complete. But, in that case, the sendi reverts to the PML, where there is
>> already code to allocate a descriptor. So, each sendi function (in each
>> BTL that has a sendi function) must have code that is already in the PML
>> anyhow. This is unnecessary extra coding and not clean design.
>> Where: In each BTL that has a sendi function (only three, and there are
>> not all used) and in the function prototype and at the PML calling site.
>> When: I'd like to incorporate this in the shared-memory latency work I'm
>> doing that we're targetting for 1.3.x.
>> Timeout: Feb 27.
>> _______________________________________________
>> devel mailing list
>> devel_at_[hidden]