Re: [OMPI users] IMB-MPI1 stuck at MPI_Finalize with OpenMPI 1.10.0

Hi Zhi Any luck with the 1.10.1 nightly snapshot? Are these all being run as separate jobs (i.e., each test is executed in series using a separate mpirun)? Ralph > On Oct 15, 2015, at 11:48 AM, Jeff Squyres (jsquyres) > wrote: > > Ralph is our runtime guy; he can provide the definitive answer

Re: [OMPI users] display-map option in v1.8.8

On 10/20/2015 04:14 PM, Ralph Castain wrote: On Oct 20, 2015, at 5:47 AM, Daniel Letai > wrote: Thanks for the reply, On 10/13/2015 04:04 PM, Ralph Castain wrote: On Oct 12, 2015, at 6:10 AM, Daniel Letai > wrote: Hi, After upgrading to

Re: [OMPI users] MPI_Win_lock with MPI_MODE_NOCHECK

The title was actually not correct. I first thought that happens when using multiple tasks/threads, but I could reproduce this with one task and thread as well. Sebastian On 10/20/2015 04:21 PM, Sebastian Rettenberger wrote: Hi, there seems to be a bug in MPI_Win_lock/MPI_Win_unlock in OpenM

Re: [OMPI users] MPI_Win_lock with MPI_MODE_NOCHECK

I filed this as https://github.com/open-mpi/ompi/issues/1049. Thanks for the bug report! > On Oct 21, 2015, at 8:23 AM, Sebastian Rettenberger > wrote: > > The title was actually not correct. I first thought that happens when using > multiple tasks/threads, but I could reproduce this with on

[OMPI users] hcoll dependency on mxm configure error

Hello All, I'm currently trying to install 1.10.0 with hcoll and mxm, and am getting an error during configure: --- MCA component coll:hcoll (m4 configuration macro) checking for MCA component coll:hcoll compile mode... static checking hcoll/api/hcoll_api.h usability... yes checking hcoll/api/

Re: [OMPI users] hcoll dependency on mxm configure error

I should probably point out that libhcoll.so does not know where libmxm.so is: [dshrader@zo-fe1 ~]$ ldd /opt/mellanox/hcoll/lib/libhcoll.so linux-vdso.so.1 => (0x7fffb2f1f000) libibnetdisc.so.5 => /usr/lib64/libibnetdisc.so.5 (0x7fe31bd0b000) libmxm.so.2 => not

Re: [OMPI users] hcoll dependency on mxm configure error

Hi David, what linux distro do you use? (and mofed version)? Do you have /etc/ld.conf.d/mxm.conf file? Can you please try add LD_LIBRARY_PATH=/opt/mellanox/mxm/lib ./configure ? Thanks On Wed, Oct 21, 2015 at 6:40 PM, David Shrader wrote: > I should probably point out that libhcoll.so does

Re: [OMPI users] hcoll dependency on mxm configure error

We're using TOSS which is based on Red Hat. The current version we're running is based on Red Hat 6.6. I'm actually not sure what mofed version we're using right now based on what I can find on the system and the admins over that are out. I'll get back to you on that as soon as I know. Using

Re: [OMPI users] hcoll dependency on mxm configure error

could you please check if you have file /etc/ld.so.conf.d/mxm.conf on your system? it will help us understand why hcoll did not detect libmxm.so at the 1st attempt. Thanks On Wed, Oct 21, 2015 at 7:19 PM, David Shrader wrote: > We're using TOSS which is based on Red Hat. The current version we'

Re: [OMPI users] hcoll dependency on mxm configure error

I'm sorry I missed reporting on that. I do not have /etc/ld.so.conf.d/mxm.conf. Interestingly enough, the rpm reports that it does include that file, but it isn't there: [dshrader@zo-fe1 serial]$ rpm -qa | grep mxm mxm-3.4.3065-1.x86_64 [dshrader@zo-fe1 serial]$ rpm -ql mxm-3.4.3065-1.x86_64

Re: [OMPI users] openib issue with 1.6.5 but not later releases

Please see inline. (Liran, can you please comment) > >> >> So, is this setting required if there are multiple IB interfaces (as >> when there are multiple eth interfaces)? What is curious is that >> there is only one interface visible from the container. Does the >> openib btl look deeper and fi

Re: [OMPI users] hcoll dependency on mxm configure error

It turns out that stuff in /etc is in RAM, so the mxm.conf wasn't there because that area hadn't been refreshed yet, either by the admin manually pushing it out or by rebooting. The admins pushed it out, and now ldd on libhcoll.so resolves the libmxm.so dependency. And, configure works without

[OMPI users] Questions about non-blocking collective calls...

Hi, A long time ago (in 2002) we programmed here a non-blocking MPI_Igather with equivalent calls to MPI_Isend/MPI_Irecv (see the 2 attached files). A very convenient advantage of this version, is that I can do some work on the root process as soon as it start receiving data... Then, it wait

Re: [OMPI users] Questions about non-blocking collective calls...

Eric, #1 MPI_Igather uses only one MPI_Request, and it is marked as completed when all data has been received. so no, you cannot process data as it is received. (and btw, that would require extra subroutines to ask which piece of data has already been received) #2 maybe not ... a tree based