Thanks! I'll put it through its paces ASAP.
On Fri, 2011-03-11 at 12:34 -0500, Jeff Squyres wrote:
> The only difference is the addition of the "affinity" MPI extension that was
> missing in 1.5.2.
>
> It seems to be ok for me. If no one else finds any problems, I'll release it
> Sunday or so
On Mar 10, 2011, at 21:54 , Ralph Castain wrote:
> Future developers? Code? What are you talking about???
>
> This isn't in the code base, nor is it "code" - it is config options in the
> private platform files for configuring clusters of contributors. We -never-
> review what is in that area,
Removing thread support is _NOT_ an option
(https://svn.mpi-forum.org/trac/mpi-forum-web/wiki/MPI3Hybrid).
Unlike the usual claims on this mailing list, MPI_THREAD_MULTIPLE had been
fully supported for several BTLs in Open MPI
(http://www.springerlink.com/content/lmh1144p51317313/). The long te
The only difference is the addition of the "affinity" MPI extension that was
missing in 1.5.2.
It seems to be ok for me. If no one else finds any problems, I'll release it
Sunday or so.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/do
On Mar 11 2011, Eugene Loh wrote:
The idea would be to hardwire support for MPI_THREAD_MULTIPLE to be off,
just as we have done for progress threads. Threads might still be used
for other purposes -- e.g., ORTE, openib async thread, etc.
That's what I was assuming, too. Threads used behind
