Re: [OMPI users] Abort/ Deadlock issue in allreduce

2016-12-09 Thread Gilles Gouaillardet
Folks, the problem is indeed pretty trivial to reproduce i opened https://github.com/open-mpi/ompi/issues/2550 (and included a reproducer) Cheers, Gilles On Fri, Dec 9, 2016 at 5:15 AM, Noam Bernstein wrote: > On Dec 8, 2016, at 6:05 AM, Gilles Gouaillardet > wrote: > > Christof, > > > Ther

Re: [OMPI users] Abort/ Deadlock issue in allreduce

2016-12-09 Thread Christof Koehler
Hello, our case is. The libwannier.a is a "third party" library which is built seperately and the just linked in. So the vasp preprocessor never touches it. As far as I can see no preprocessing of the f90 source is involved in the libwannier build process. I finally managed to set a breakpoint a

Re: [OMPI users] Abort/ Deadlock issue in allreduce

2016-12-09 Thread Noam Bernstein
> On Dec 9, 2016, at 3:39 AM, Christof Koehler > wrote: > > Hello, > > our case is. The libwannier.a is a "third party" > library which is built seperately and the just linked in. So the vasp > preprocessor never touches it. As far as I can see no preprocessing of > the f90 source is involved i

Re: [OMPI users] How to yield CPU more when not computing (was curious behavior during wait for broadcast: 100% cpu)

2016-12-09 Thread Andreas Schäfer
On 14:25 Thu 08 Dec , Dave Love wrote: > Jeff Hammond writes: > > >> > >> > >> > Note that MPI implementations may be interested in taking advantage of > >> > https://software.intel.com/en-us/blogs/2016/10/06/intel- > >> xeon-phi-product-family-x200-knl-user-mode-ring-3-monitor-and-mwait. > >