Open MPI logo

Open MPI Development Mailing List Archives

  |   Home   |   Support   |   FAQ   |   all Development mailing list

Subject: Re: [OMPI devel] RFC: Move the Open MPI communication infrastructure in OPAL
From: Jeff Squyres (jsquyres) (jsquyres_at_[hidden])
Date: 2014-07-10 19:03:56

FWIW: I can't speak for other BTL maintainers, but I'm out of the office for the next week, and the usnic BTL will be standing still during that time. Once I return, I will be making additional changes in the usnic BTL (new features, updates, ...etc.).

So if you have the cycles, doing it in the next week or so would be good because at least there will be no conflicts with usnic BTL concurrent development. :-)

On Jul 10, 2014, at 2:56 PM, Ralph Castain <rhc_at_[hidden]> wrote:

> George: any update on when this will happen?
> On Jun 4, 2014, at 9:14 PM, George Bosilca <bosilca_at_[hidden]> wrote:
>> WHAT: Open our low-level communication infrastructure by moving all
>> necessary components
>> (btl/rcache/allocator/mpool) down in OPAL
>> WHY: All the components required for inter-process communications are
>> currently deeply integrated in the OMPI
>> layer. Several groups/institutions have express interest
>> in having a more generic communication
>> infrastructure, without all the OMPI layer dependencies.
>> This communication layer should be made
>> available at a different software level, available to
>> all layers in the Open MPI software stack. As an
>> example, our ORTE layer could replace the current OOB
>> and instead use the BTL directly, gaining
>> access to more reactive network interfaces than TCP.
>> Similarly, external software libraries could take
>> advantage of our highly optimized AM (active message)
>> communication layer for their own purpose.
>> UTK with support from Sandia, developped a version of
>> Open MPI where the entire communication
>> infrastucture has been moved down to OPAL
>> (btl/rcache/allocator/mpool). Most of the moved
>> components have been updated to match the new schema,
>> with few exceptions (mainly BTLs
>> where I have no way of compiling/testing them). Thus,
>> the completion of this RFC is tied to
>> being able to completing this move for all BTLs. For
>> this we need help from the rest of the Open MPI
>> community, especially those supporting some of the BTLs.
>> A non-exhaustive list of BTLs that
>> qualify here is: mx, portals4, scif, udapl, ugni, usnic.
>> WHERE: (updated today with respect to
>> trunk r31952)
>> TIMEOUT: After all the BTLs have been amended to match the new
>> location and usage. We will discuss
>> the last bits regarding this RFC at the Open MPI
>> developers meeting in Chicago, June 24-26. The
>> RFC will become final only after the meeting.
>> _______________________________________________
>> devel mailing list
>> devel_at_[hidden]
>> Subscription:
>> Link to this post:
> _______________________________________________
> devel mailing list
> devel_at_[hidden]
> Subscription:
> Link to this post:

Jeff Squyres
For corporate legal information go to: