If the guidelines are made for the BTLs Sun will handle the udapl btl.
We can also help in testing too.
--td
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
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
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
There is a priority change for us. 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.
Jeff Squyres wrote:
The MPICH guys presented TCP results with THREAD_MULTIPLE at Euro PVM/
MPI and frankly, I was amazed that it worked at all.
I seriously doubt that we're going to advance the state of threading
on the 1.2 series (which is nowhere as close as it is on the 1.3
series).
The MPICH guys presented TCP results with THREAD_MULTIPLE at Euro PVM/
MPI and frankly, I was amazed that it worked at all.
I seriously doubt that we're going to advance the state of threading
on the 1.2 series (which is nowhere as close as it is on the 1.3
series).
On Nov 28, 2007, at
Ya, the front page needs some updating...
On Nov 28, 2007, at 11:32 AM, Brian W. Barrett wrote:
On Wed, 28 Nov 2007, Jeff Squyres wrote:
We've had a few users complain about trying to use THREAD_MULTIPLE
lately and having it not work.
Here's a proposal: why don't we disable it (at least in
On Wed, 28 Nov 2007, Jeff Squyres wrote:
We've had a few users complain about trying to use THREAD_MULTIPLE
lately and having it not work.
Here's a proposal: why don't we disable it (at least in the 1.2
series)? Or, at the very least, put in a big stderr warning that is
displayed when
