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] THREAD_MULTIPLE
From: Terry Dontje (Terry.Dontje_at_[hidden])
Date: 2007-11-28 14:09:32

If the guidelines are made for the BTLs Sun will handle the udapl btl.

We can also help in testing too.


George Bosilca wrote:
> Yes, "us" means UTK. Our math folks are pushing hard for this. I'll
> gladly accept any help, even if it's only for testing. For
> development, I dispose of some of my time and a 100% of a post-doc for
> few months.
> However, there are limits to what we can do. We will make sure the BTL
> threading requirements are clearly specified, and we will take care of
> the BTLs we already worked on (TCP, self, SM, MX). I hope that once
> the BTL interface is defined, others can make sure their BTL follow
> the guidelines.
> Thanks,
> george.
> On Nov 28, 2007, at 1:34 PM, Jeff Squyres wrote:
>> On Nov 28, 2007, at 1:26 PM, George Bosilca wrote:
>>> There is a priority change for us.
>> "us" = UTK?
>>> It's definitively time to have a fully supported MPI_THREAD_MULTIPLE
>>> mode in Open MPI. I'm working to figure out how and where to get the
>>> cycles for this. I expect to start working on it in January. So, the
>>> good news is that 1.3 will have thread support.
>> That will be great. Do you really think that you can finish the
>> THREAD_MULTIPLE work by yourself?
>> Cisco can provide some resources for testing (in the environments that
>> we care about :-) ), but probably not for development.
>> --
>> Jeff Squyres
>> Cisco Systems
>> _______________________________________________
>> devel mailing list
>> devel_at_[hidden]
> ------------------------------------------------------------------------
> _______________________________________________
> devel mailing list
> devel_at_[hidden]