I think the issue is that the revert may have resulted in having to set both —enable-mpi-thread-multiple and —enable-opal-multi-threads, and Mike is asking that the first automatically turn on the second
> On Nov 5, 2014, at 8:51 AM, Jeff Squyres (jsquyres) <jsquy...@cisco.com> > wrote: > > On Nov 5, 2014, at 11:43 AM, Mike Dubman <mi...@dev.mellanox.co.il> wrote: > >> sorry, >>>>> "now we use only this "--enable-mpi-thread-multiple" and it worked." >> >> I meant it worked fine before the "configure logic" changes. > > It went back to the way it was in in the v1.6 series. > > The issue is that --enable-mpi-thread-multiple carries a performance penalty > on the v1.8 branch. On master, we need to sort these kinds of issues out so > that there is no/minimal performance penalty. > > -- > Jeff Squyres > jsquy...@cisco.com > For corporate legal information go to: > http://www.cisco.com/web/about/doing_business/legal/cri/ > > _______________________________________________ > devel mailing list > de...@open-mpi.org > Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel > Link to this post: > http://www.open-mpi.org/community/lists/devel/2014/11/16208.php
