Re: [OMPI users] openib/mpi_alloc_mem pathology

2017-03-13 Thread Paul Kapinos
Nathan, unfortunately '--mca memory_linux_disable 1' does not help on this issue - it does not change the behaviour at all. Note that the pathological behaviour is present in Open MPI 2.0.2 as well as in /1.10.x, and Intel OmniPath (OPA) network-capable nodes are affected only. The known

Re: [OMPI users] MPI_Comm_accept()

2017-03-13 Thread Adam Sylvester
As a follow-up, I tried this with Open MPI 1.10.4 and this worked as expected (the port formatting looks really different): $ mpirun -np 1 ./server Port name is 1286733824.0;tcp://10.102.16.135:43074 +1286733825.0;tcp://10.102.16.135::300 Accepted! $ mpirun -np 1 ./client

Re: [OMPI users] MPI_Comm_accept()

2017-03-13 Thread r...@open-mpi.org
You should consider it a bug for now - it won’t work in the 2.0 series, and I don’t think it will work in the upcoming 2.1.0 release. Probably will be fixed after that. > On Mar 13, 2017, at 5:17 AM, Adam Sylvester wrote: > > As a follow-up, I tried this with Open MPI

Re: [OMPI users] "No objects of the specified type were found on at least one node"

2017-03-13 Thread Angel de Vicente
Brice Goglin writes: > Ok, that's a very old kernel on a very old POWER processor, it's > expected that hwloc doesn't get much topology information, and it's > then expected that OpenMPI cannot apply most binding policies. Just in case it can add anything, I tried with an

[OMPI users] Failed to create a queue pair (QP) error

2017-03-13 Thread Ilchenko Evgeniy
HI! I trying run parallel "Hello, World!" program using OpenMPI on cluster. My program written on C++ and compiled with this OpenMPI soft (mpicxx). Cluster uses InfiniBand and TCP networks. I install OpenMPI soft in my home directory on manager node. After this I get to the node via SSH (ssh

Re: [OMPI users] MPI_Comm_accept()

2017-03-13 Thread Adam Sylvester
Bummer - thanks for the update. I will revert back to 1.10.x for now then. Should I file a bug report for this on GitHub or elsewhere? Or if there's an issue for this already open, can you point me to it so I can keep track of when it's fixed? Any best guess calendar-wise as to when you expect

[OMPI users] Lustre support uses deprecated include.

2017-03-13 Thread Åke Sandgren
Hi! The lustre support in ompi/mca/fs/lustre/fs_lustre.h is using a deprecated include. #include is deprecated in newer lustre versions (at least from 2.8) and #include should be used instead. -- Ake Sandgren, HPC2N, Umea University, S-90187 Umea, Sweden Internet: a...@hpc2n.umu.se

Re: [OMPI users] Lustre support uses deprecated include.

2017-03-13 Thread Edgar Gabriel
thank you for the report, it is on my to do list. I will try to get the configure logic to recognize which file to use later this, should hopefully be done for 2.0.3 and 2.1.1 series. Thanks Edgar On 3/13/2017 8:55 AM, Åke Sandgren wrote: Hi! The lustre support in