On Nov 3, 2009, at 10:02 AM, Mondrian Nuessle wrote:
hm, I did not set any threading related options in configure, so I
guess threading was not disabled.
I compiled it again with the following configure options,
--enable-debug --enable-memchecker --enable-mem-debug --disable-ft-
thread --di
Hi,
hm, I did not set any threading related options in configure, so I guess
threading was not disabled.
I compiled it again with the following configure options,
--enable-debug --enable-memchecker --enable-mem-debug --disable-ft-thread
--disable-progress-threads --disable-mpi-threads
and the
Note that the problems Chris is talking about *should* only occur if
you have compiled Open MPI with multi-threaded support. Did you do
that, perchance?
On Nov 2, 2009, at 9:26 AM, Mondrian Nuessle wrote:
Hi Christopher,
>> Do you have any suggestions how to investigate this situation?
>
Hi Christopher,
>> Do you have any suggestions how to investigate this situation?
>
> Have you got OMPI_ENABLE_DEBUG defined? The symptoms of what you are
> seeing sound like what might happen if debug is off and you trigger an
> issue I posted about here related to thread safety of mpool.
unfort
Hi Mondrian,
On Mon, 02 Nov 2009 13:22:11 +0100
Mondrian Nuessle wrote:
>
> If I turn on mpi_leave_pinned (and thus the registration cache is
> actually used), I see occasional memory corruption issues for example
> when I call MPI_Allreduce often.
>
> Debugging with valgrind did not lead to an
Hi everybody!
We are working on a new, experimental interconnection network (the EXTOLL
network) and I am currently working on a MTL
component for that hardware. Actually, it works quite good :-)
Recently I included the RDMA mpool component for memory registration caching
into my code. Again, t
