Re: [OMPI users] ScaLapack tester fails with 2.0.1, works with 1.10.4; Intel Omni-Path

2016-11-22 Thread Christof Koehler
Hello again, I tried to replicate the situation on the workstation at my desk, running ubuntu 14.04 (gcc 4.8.4) and with the OS supplied lapack and blas libraries. With openmpi 2.0.1 (mpirun -np 4 xdsyevr) I get "136 tests completed and failed." with the "IL, IU, VL or VU altered by PDSYEVR" mes

Re: [OMPI users] valgrind invalid read

2016-11-22 Thread Yann Jobic
Hi, I manually changed the file. Moreover i also tried the 1.8.4 openmpi version. I still have this invalid read. Am i doing something wrong ? Thanks, Yann Le 22/11/2016 à 00:50, Gilles Gouaillardet a écrit : Yann, this is a bug that was previously reported, and the fix is pending on

Re: [OMPI users] ScaLapack tester fails with 2.0.1, works with 1.10.4; Intel Omni-Path

2016-11-22 Thread Gilles Gouaillardet
Christoph, out of curiosity, could you try to mpirun --mca coll ^tuned ... and see if it helps ? Cheers, Gilles On Tue, Nov 22, 2016 at 7:21 PM, Christof Koehler wrote: > Hello again, > > I tried to replicate the situation on the workstation at my desk, > running ubuntu 14.04 (gcc 4.8.4) and

Re: [OMPI users] valgrind invalid read

2016-11-22 Thread Gilles Gouaillardet
Yann, my bad, the patch you need is at https://github.com/open-mpi/ompi/pull/2368.patch sorry for the confusion, Gilles On Tue, Nov 22, 2016 at 8:33 PM, Yann Jobic wrote: > Hi, > > I manually changed the file. Moreover i also tried the 1.8.4 openmpi > version. > > I still have this invalid re

Re: [OMPI users] ScaLapack tester fails with 2.0.1, works with 1.10.4; Intel Omni-Path

2016-11-22 Thread Christof Koehler
Hello, On Tue, Nov 22, 2016 at 10:35:57PM +0900, Gilles Gouaillardet wrote: > Christoph, > > out of curiosity, could you try to > mpirun --mca coll ^tuned ... > and see if it helps ? No, at least not for the workstation example. I will test with my laptop (debian stable) tomorrow. Thank you all

[OMPI users] Follow-up to Open MPI SC'16 BOF

2016-11-22 Thread Howard Pritchard
Hello Folks, This is a followup to the question posed at the SC’16 Open MPI BOF: Would the community prefer to have a v2.2.x limited feature but backwards compatible release sometime in 2017, or would the community prefer a v3.x (not backwards compatible but potentially more features) sometime in

Re: [OMPI users] Follow-up to Open MPI SC'16 BOF

2016-11-22 Thread Jeff Hammond
> > > >1. MPI_ALLOC_MEM integration with memkind > > It would sense to prototype this as a standalone project that is integrated with any MPI library via PMPI. It's probably a day or two of work to get that going. Jeff -- Jeff Hammond jeff.scie...@gmail.com http://jeffhammond.github.io/ ___

Re: [OMPI users] Follow-up to Open MPI SC'16 BOF

2016-11-22 Thread Howard Pritchard
Hi Jeff, I don't think it was the use of memkind itself, but a need to refactor the way Open MPI is using info objects that was the issue. I don't recall the details. Howard 2016-11-22 16:27 GMT-07:00 Jeff Hammond : > >> >>1. MPI_ALLOC_MEM integration with memkind >> >> It would sense to