Re: [OMPI users] PGI 8.0-4 doesn't like ompi/mca/op/op.h

2009-03-16 Thread Samuel Sarholz
Hi, I am pretty sure that C++ has no restrict keyword (only C99), so IMHO it's not the compilers fault is not compiling. You probably want to turn restricts off for C++ by default, unless you know the compiler supports it. best regards, Samuel smime.p7s Description: S/MIME Cryptographic Si

Re: [OMPI users] /usr/bin/ld: skipping incompatible /usr/local/lib/libgcc_s.so when searching for -lgcc_s

2009-02-13 Thread Samuel Sarholz
Hi Gary, that is a linker warning. You probably have a libgcc_s.so in 32 and 64 bit. The linker finds the "wrong" version first and skips it. After that the matching one is linked and thus your program runs. So nothing to worry about. To avoid the warning you can switch the (default) search o

Re: [OMPI users] Heterogeneous OpenFabrics hardware

2009-01-27 Thread Samuel Sarholz
Hi, I can think of a few scenarios where interoperability would be helpful, but I guess in most case you can live without. 1. Some university departments buy tiny clusters (4-8 nodes) and when more projects/funding become available the next one. Thus ending up with 2-4 different CPU generation

Re: [OMPI users] Performance: MPICH2 vs OpenMPI

2008-10-08 Thread Samuel Sarholz
Hi, my experience is that OpenMPI has slightly less latency and less bandwidth than Intel MPI (which is based on mpich2) using InfiniBand. I don't remember the numbers using shared memory. As you are seeing a huge difference, I would suspect that either something with your compilation is stra

Re: [OMPI users] mpirun, paths and xterm again (xserver problem solved; library problem still there)

2008-09-24 Thread Samuel Sarholz
Hi, I think the problem is that xterm (probably) has the userid bit set and thus deletes the LD_LIBRARY_PATH. Try setting the path again before you start gdb, e.g: mpirun -n 2 -x DISPLAY=:0.0 xterm -e LD_LIBRARY_PATH= or use the -Wl,-rpath= to compiler the search path into the executable. b

Re: [OMPI users] How can I pass my user limits (stacksize, etc.) to mpirun in OpenMPI

2008-09-10 Thread Samuel Sarholz
Hi Jeff, I think setting global limits will not help in this case as the limits like stacksize need to be program specific. So far I am using wrappers, however the solution is a bit nasty. If there is another way it would be great. Hoever I doubt that there is a way as the FAQ states: More

[OMPI users] Number of file handles limiting the number off processes?

2008-07-10 Thread Samuel Sarholz
Hi, mpiexec seems to need a file handle per started process. By default the number of file handles is set to 1024 here, thus I can start about 900 something processes. With higher numbers I get mca_oob_tcp_accept: accept() failed: Too many open files (24). If I decrease the file handles on th

Re: [OMPI users] libibverbs and openmpi 1.2.6

2008-06-05 Thread Samuel Sarholz
ncies of libmpi (and friends). thanks for the hint. You are right we used --enable-static with 1.2.6. best regards Samuel P.S.: I liked you videos btw. -- Dipl.-Inform. Samuel Sarholz- High Performance Computing, RWTH Aachen University, Center for Computing and Communication, Seffenter W

Re: [OMPI users] libibverbs and openmpi 1.2.6

2008-06-05 Thread Samuel Sarholz
libibverbs? Yes, ldd shows a dependency. Best regards, Samuel -- Dipl.-Inform. Samuel Sarholz- High Performance Computing, RWTH Aachen University, Center for Computing and Communication, Seffenter Weg 23, 52074 Aachen (Germany), Office: 2.13 Tel: +49 241/80-24915 - Fax: +49 241/80-22134

[OMPI users] libibverbs and openmpi 1.2.6

2008-06-05 Thread Samuel Sarholz
linked which doen't exist on some of the machines. Is there a way to get programs compiled on a IB machine running them on machines without IB? (remove the dependency to libibverbs from openmpi 1.2.6) best regards, Samuel -- Dipl.-Inform. Samuel Sarholz- High Performance Computing,

[OMPI users] Communicators in Fortran and C

2008-06-05 Thread Samuel Sarholz
Hi, I have problems running a Fortran program which is calling a C library with OpenMPI. The problem is that the Fortan part has a communicator which is passed to the C library. And if I understand the headers right a communicator is an integer in fortran, but a struct on the C side of openm