Re: [OMPI users] OpenMPI 1.8.2 problems on CentOS 6.3

I’m not sure our man pages are good enough to answer your question, but here is the URL http://www.open-mpi.org/doc/v1.8/ I’m a tad tied up right now, but I’ll try to address this prior to 1.8.5 release. Thanks for all that debug effort! Helps a bunch. > On

Re: [OMPI users] OpenMPI 1.8.2 problems on CentOS 6.3

Ralph, I've finally had some luck using the following: $MPI_DIR/bin/mpirun -np $NSLOTS --report-bindings --hostfile hostfile-single --mca btl_tcp_if_include eth0 --hetero-nodes --use-hwthread-cpus --prefix $MPI_DIR $BENCH_DIR/$APP_DIR/$APP_BIN Where $NSLOTS was 56 and my hostfile

Re: [OMPI users] 1.8.4 behaves completely different from 1.6.5

Here is a stackdump from inside the debugger (because it gives filenames and line numbers): Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7f1eb6bfd700 (LWP 24847)] 0x00366aa79252 in _int_malloc () from /lib64/libc.so.6 (gdb) bt #0 0x00366aa79252 in

Re: [OMPI users] Different HCA from different OpenMP threads (same rank using MPI_THREAD_MULTIPLE)

Easiest way is to follow the link at the bottom of the message: http://www.open-mpi.org/mailman/listinfo.cgi/users > On Apr 7, 2015, at 10:39 AM, Abdul Rahman Riza wrote: > > how to unsubscribe? > > On Tue, Apr 7,

Re: [OMPI users] Different HCA from different OpenMP threads (same rank using MPI_THREAD_MULTIPLE)

how to unsubscribe? On Tue, Apr 7, 2015 at 4:45 PM, Filippo Spiga wrote: > Thanks Rolf and Ralph for the replies! > > On Apr 6, 2015, at 10:37 PM, Ralph Castain wrote: > > That said, you can certainly have your application specify a > thread-level

Re: [OMPI users] Different HCA from different OpenMP threads (same rank using MPI_THREAD_MULTIPLE)

how to unsubscribe? On Mon, Apr 6, 2015 at 4:45 PM, Filippo Spiga wrote: > Dear Open MPI developers, > > I wonder if there is a way to address this particular scenario using MPI_T > or other strategies in Open MPI. I saw a similar discussion few days ago, I > assume the

Re: [OMPI users] OpenMPI 1.8.4 - Java Library - allToAllv()

I’m afraid we’ll have to get someone from the Forum to interpret (Howard is a member as well), but here is what I see just below that, in the description section: The type signature associated with sendcounts[j], sendtype at process i must be equal to the type signature associated with

Re: [OMPI users] OpenMPI 1.8.4 - Java Library - allToAllv()

Hello, Thanks for your description. I'm currently doing allToAll() prior to allToAllV(), to communicate length of expected messages. . BUT, I still strongly believe that the right implementation of this method is something that I expected earlier! If you check the MPI specification here:

Re: [OMPI users] http://www.open-mpi.org/doc/current/man3/MPI_Win_lock_all.3.php

Hi Thomas, Thanks very much for pointing this out. Will fix shortly. Howard On Apr 7, 2015 5:35 AM, "Thomas Jahns" wrote: > Hello, > > I think above web site lists the Fortran syntax section incorrectly as > > INCLUDE ’mpif.h’ > MPI_WIN_LOCK(ASSERT, WIN, IERROR) > INTEGER

Re: [OMPI users] OpenMPI 1.8.4 - Java Library - allToAllv()

Hi HR, Sorry for not noticing the receive side earlier, but as Ralph implied earlier in this thread, the MPI standard has more strict type matching for collectives than for point to point. Namely, the number of bytes the receiver expects to receive from a given sender in the alltoallv must match

[OMPI users] http://www.open-mpi.org/doc/current/man3/MPI_Win_lock_all.3.php

Hello, I think above web site lists the Fortran syntax section incorrectly as INCLUDE ’mpif.h’ MPI_WIN_LOCK(ASSERT, WIN, IERROR) INTEGER ASSERT, WIN, IERROR when there should be MPI_WIN_LOCK_ALL(ASSERT, WIN, IERROR) instead. Regards, Thomas smime.p7s Description: S/MIME Cryptographic

Re: [OMPI users] Different HCA from different OpenMP threads (same rank using MPI_THREAD_MULTIPLE)

Thanks Rolf and Ralph for the replies! On Apr 6, 2015, at 10:37 PM, Ralph Castain wrote: > That said, you can certainly have your application specify a thread-level > binding. You’d have to do the heavy lifting yourself in the app, I’m afraid, > instead of relying on us to

Re: [OMPI users] OpenMPI 1.8.4 - Java Library - allToAllv()

Hello, If I set the size2 values according to your suggestion, which is the same values as on sending nodes, it works fine. But by definition it does not need to be exactly the same as the length of sent data, and it is just a maximum length of expected data to receive. If not, it is inevitable