Hey Jeff, now we use only this "--enable-mpi-thread-multiple" and it worked. does it mean that now we need to pass "--enable-mpi-thread-multiple --enable-opal-multi-threads" to get it working again? Maybe if one of the params used it should enable another one as well?
Thanks On Wed, Nov 5, 2014 at 3:47 PM, Jeff Squyres (jsquyres) <jsquy...@cisco.com> wrote: > $ ./configure --help |& grep thread > code will ever run in SMP or multi-threaded > --enable-opal-multi-threads > Enable thread support inside OPAL (default: > --enable-mpi-thread-multiple > Enable MPI_THREAD_MULTIPLE support (default: > --with-threads Set thread type (posix) > > > > On Nov 5, 2014, at 3:32 AM, Joshua Ladd <jladd.m...@gmail.com> wrote: > > > Jeff, > > > > What configure voodoo do we need to add to our MTT to get this > functional again? > > > > Josh > > > > On Tue, Nov 4, 2014 at 12:33 PM, Ralph Castain <rhc.open...@gmail.com> > wrote: > > That would be correct - we restored some configure flags that are > required to make multi-thread programs work. Jeff can probably provide more > info. > > > > > >> On Nov 4, 2014, at 9:15 AM, Alina Sklarevich <ali...@dev.mellanox.co.il> > wrote: > >> > >> Hi, > >> > >> We observe a hang when running the multi-threading support test > "latency.c" (attached to this report), which uses MPI_THREAD_MULTIPLE. > >> > >> The hang happens immediately at the begining of the test and is > reproduced in the v1.8 release branch. > >> > >> The command line to reproduce the behavior is: > >> > >> $ mpirun --map-by node --bind-to core -display-map -np 2 -mca pml ob1 > -mca btl tcp,self ./thread-tests-1.1/latency > >> > >> The last commit with which the hang doesn't reproduce is: > >> commit: e4d4266d9c69e > >> > >> > >> > >> And problems begin after commit: > >> > >> > >> > >> commit 09b867374e9618007b81bfaf674ec6df04548bed > >> > >> Author: Jeff Squyres <jsquy...@cisco.com> > >> > >> Date: Fri Oct 31 12:42:50 2014 -0700 > >> > >> > >> > >> Revert most of > open-mpi/ompi@6ef938de3fa9ca0fed2c5bcb0736f65b0d8803af > >> > >> > >> > >> Is this expected behavior? In other words, should we not expect any > stable release in the 1.8.x series to be able to use MPI_THREAD_MULTIPLE > with even the TCP and SM BTLs? > >> > >> > >> > >> Please advise. > >> > >> > >> > >> Thanks, > >> > >> Alina. > >> > >> > >> > >> > >> > >> <latency.c>_______________________________________________ > >> 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/16175.php > > > > > > _______________________________________________ > > 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/16177.php > > > > _______________________________________________ > > 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/16194.php > > > -- > 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/16196.php > -- Kind Regards, M.
