To tell you all what noone wanted to tell me, yes, it does seem to be
the memory manager. Compiling everything with
--with-memory-manager=none returns the vmem use to the more reasonable
~100MB per process (down from >8GB).
I take it this may affect my peak bandwidth over infiniband. What's the
Arif,
It looks like your system is 64 bit by default and it therefore
doesn't pick up the 32 bit libraries automatically at the link step
(note the -L/.../x86_64-suse-linux/lib entries prior to the
correspond entries pointing to the 32 bit library versions). I don't
use suse linux so
Hi,
OS: SLES10 SP1
OFED: 1.3
openmpi: 1.2 1.2.5 1.2.6
compilers: gcc g++ gfortran
I am creating a 32-bit build of openmpi on an Infiniband cluster, and the
compilation gets stuck, If I use the
/usr/lib64/gcc/x86_64-suse-linux/4.1.2/32/libstdc++.so library manually it
compiles that piece of cod
It feels like OMPI is somehow looking for the help files in the wrong
place. Were they moved after OMPI was installed? How did you install
OMPI?
On May 16, 2008, at 10:30 AM, Alex L. wrote:
Hello Everybody,
i got a little bit annoying situation with OMPI error messages
on a RHEL 4-some
