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: George Bosilca (bosilca_at_[hidden])
Date: 2014-07-15 02:06:25


Ralph,

There are two reasons that prevent me from pushing this RFC forward.

1. Minor: The code has some minor issues related to the last set of BTL/PML
changes, and I didn't found the time to fix them.

2. Major: Not all BTLs have been updated and validated. What we need at
this point from their respective developers is a little help with the
validation process. We need to validate that the new code works as expected
and passes all tests.

The move will be ready to go as soon as all BTL developers raise the green
flag. I got it from Jeff (but the last USNIC commit broke something), and
myself. In other words, TCP, self, SM and USNIC are good to go. For the
others, as I didn't heard back from their developers/maintainers, I assume
they are not yet ready. Here I am referring to OpenIB, Portals4, Scif,
smcuda, ugni, usnic and vader.

  George.

PS: As a reminder the code is available at
https://bitbucket.org/bosilca/ompi-btl

On Fri, Jul 11, 2014 at 3:17 PM, Pritchard, Howard P <howardp_at_[hidden]>
wrote:

> Hi Folks,
>
> Now work is planned for the uGNI BTL at this time either.
>
> Howard
>
>
> -----Original Message-----
> From: devel [mailto:devel-bounces_at_[hidden]] On Behalf Of Jeff Squyres
> (jsquyres)
> Sent: Thursday, July 10, 2014 5:04 PM
> To: Open MPI Developers List
> Subject: Re: [OMPI devel] RFC: Move the Open MPI communication
> infrastructure in OPAL
>
> 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: bitbucket.org/bosilca/ompi-btl (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: http://www.open-mpi.org/mailman/listinfo.cgi/devel
> >> Link to this post:
> >> http://www.open-mpi.org/community/lists/devel/2014/06/14974.php
> >
> > _______________________________________________
> > devel mailing list
> > devel_at_[hidden]
> > Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
> > Link to this post:
> > http://www.open-mpi.org/community/lists/devel/2014/07/15100.php
>
>
> --
> Jeff Squyres
> jsquyres_at_[hidden]
> For corporate legal information go to:
> http://www.cisco.com/web/about/doing_business/legal/cri/
>
> _______________________________________________
> devel mailing list
> devel_at_[hidden]
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
> Link to this post:
> http://www.open-mpi.org/community/lists/devel/2014/07/15104.php
> _______________________________________________
> devel mailing list
> devel_at_[hidden]
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
> Link to this post:
> http://www.open-mpi.org/community/lists/devel/2014/07/15111.php
>