Re: [OMPI devel] THREAD_MULTIPLE
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 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 de...@open-mpi.org http://www.open-mpi.org/mailman/listinfo.cgi/devel ___ devel mailing list de...@open-mpi.org http://www.open-mpi.org/mailman/listinfo.cgi/devel
Re: [OMPI devel] THREAD_MULTIPLE
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 de...@open-mpi.org http://www.open-mpi.org/mailman/listinfo.cgi/devel smime.p7s Description: S/MIME cryptographic signature
Re: [OMPI devel] THREAD_MULTIPLE
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
Re: [OMPI devel] THREAD_MULTIPLE
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. Thanks, george. On Nov 28, 2007, at 1:20 PM, Terry Dontje wrote: 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). And 1.3 I think still has a way to go to before one could really say it supports THREAD_MULTIPLE. --td On Nov 28, 2007, at 12:21 PM, Richard Graham wrote: Are there not users that are using THREAD_MULTIPLE successfully, or is this on the trunk ? We know that the code is not where it needs to be, but if this takes away current functionality, I would prefer to display a warning. Rich On 11/28/07 11:27 AM, "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 THREAD_MULTIPLE is selected? Comments? ___ devel mailing list de...@open-mpi.org http://www.open-mpi.org/mailman/listinfo.cgi/devel ___ devel mailing list de...@open-mpi.org http://www.open-mpi.org/mailman/listinfo.cgi/devel smime.p7s Description: S/MIME cryptographic signature
Re: [OMPI devel] THREAD_MULTIPLE
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). And 1.3 I think still has a way to go to before one could really say it supports THREAD_MULTIPLE. --td On Nov 28, 2007, at 12:21 PM, Richard Graham wrote: Are there not users that are using THREAD_MULTIPLE successfully, or is this on the trunk ? We know that the code is not where it needs to be, but if this takes away current functionality, I would prefer to display a warning. Rich On 11/28/07 11:27 AM, "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 THREAD_MULTIPLE is selected? Comments? ___ devel mailing list de...@open-mpi.org http://www.open-mpi.org/mailman/listinfo.cgi/devel
Re: [OMPI devel] THREAD_MULTIPLE
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 12:21 PM, Richard Graham wrote: Are there not users that are using THREAD_MULTIPLE successfully, or is this on the trunk ? We know that the code is not where it needs to be, but if this takes away current functionality, I would prefer to display a warning. Rich On 11/28/07 11:27 AM, "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 THREAD_MULTIPLE is selected? Comments? ___ devel mailing list de...@open-mpi.org http://www.open-mpi.org/mailman/listinfo.cgi/devel -- Jeff Squyres Cisco Systems
Re: [OMPI devel] THREAD_MULTIPLE
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 the 1.2 series)? Or, at the very least, put in a big stderr warning that is displayed when THREAD_MULTIPLE is selected? Comments? While you're disabiling it, might also want to remove the bullet from the front page of www.open-mpi.org that suggests we support it... Brian ___ devel mailing list de...@open-mpi.org http://www.open-mpi.org/mailman/listinfo.cgi/devel -- Jeff Squyres Cisco Systems
Re: [OMPI devel] THREAD_MULTIPLE
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 THREAD_MULTIPLE is selected? Comments? While you're disabiling it, might also want to remove the bullet from the front page of www.open-mpi.org that suggests we support it... Brian