Re: [O-MPI devel] couple of problems in openib mpool.

2005-08-12 Thread Galen Shipman
Hey Gleb, Sorry for the delay.. we have been doing a bit of reworking of the pml/btl so that the btl's can be shared outside of just the pml (collectives, etc). I have added the bug fix (old_reg). Will look at the assumption of non-null registration next. Thanks (and keep them coming ;-) ,

[O-MPI devel] build warnings..

2005-08-12 Thread Galen Shipman
Current build warnings: mca_base_parse_paramfile_lex.c:1664: warning: 'yy_flex_realloc' defined but not used qsort.c:163: warning: cast from pointer to integer of different size show_help_lex.c:1606: warning: 'yy_flex_realloc' defined but not used rmgr_proxy.c:237: warning: ISO C forbids conver

Re: [O-MPI devel] build warnings..

2005-08-12 Thread Brian Barrett
On Aug 12, 2005, at 9:36 AM, Galen Shipman wrote: Current build warnings: mca_base_parse_paramfile_lex.c:1664: warning: 'yy_flex_realloc' defined but not used This one is pretty much impossible to fix (it's in a file generated by lex, and isn't easy to deal with. qsort.c:163: warning: cas

[O-MPI devel] OMPI 32bit on a 64bit Linux box

2005-08-12 Thread Nathan DeBardeleben
We've got a 64bit Linux (SUSE) box here. For a variety of reasons (Java, JNI, linking in with OMPI libraries, etc which I won't get into) I need to compile OMPI 32 bit (or get 64bit versions of a lot of other libraries). I get various compile errors when I try different things, but first let m

Re: [O-MPI devel] OMPI 32bit on a 64bit Linux box

2005-08-12 Thread Brian Barrett
On Aug 12, 2005, at 3:13 PM, Nathan DeBardeleben wrote: We've got a 64bit Linux (SUSE) box here. For a variety of reasons (Java, JNI, linking in with OMPI libraries, etc which I won't get into) I need to compile OMPI 32 bit (or get 64bit versions of a lot of other libraries). I get various c

Re: [O-MPI devel] OMPI 32bit on a 64bit Linux box

2005-08-12 Thread Nathan DeBardeleben
Thanks, trying that now. While I'd like those things in the long run, they're not needed right now to test what I'm trying to test. Will let you know how it goes! (What's the problem, by the way?) -- Nathan Correspondence -

Re: [O-MPI devel] OMPI 32bit on a 64bit Linux box

2005-08-12 Thread Brian Barrett
On Aug 12, 2005, at 3:22 PM, Nathan DeBardeleben wrote: Thanks, trying that now. While I'd like those things in the long run, they're not needed right now to test what I'm trying to test. Will let you know how it goes! (What's the problem, by the way?) The problem is that I key off the t

Re: [O-MPI devel] OMPI 32bit on a 64bit Linux box

2005-08-12 Thread Nathan DeBardeleben
OK, so I reconfigured, made, etc: 137 14:29 ./configure CFLAGS=-m32 FFLAGS=-m32 --build=i586-suse-linux --enable-static --disable-shared --without-threads --prefix=/home/ndebard/local/ompi --with-devel-headers --disable-io-romio --disable-f77 138 14:48 make clean all install But

Re: [O-MPI devel] OMPI 32bit on a 64bit Linux box

2005-08-12 Thread Jeff Squyres
That's a neat one. mpicc shouldn't care about any of this stuff -- it's a trivial C++ program that invokes none of the MCA framework stuff, etc. I'll try to replicate. Just out of curiosity -- do other C++ applications work nicely in 32 bit on that machine? (particularly ones that use std::

Re: [O-MPI devel] OMPI 32bit on a 64bit Linux box

2005-08-12 Thread Jeff Squyres
Actually, Brian just pointed out the problem -- you also need to set CXXFLAGS=-m32. On Aug 12, 2005, at 5:15 PM, Jeff Squyres wrote: That's a neat one. mpicc shouldn't care about any of this stuff -- it's a trivial C++ program that invokes none of the MCA framework stuff, etc. I'll try to r

[O-MPI devel] Memory manager changes

2005-08-12 Thread Brian Barrett
Hi all - For those not on the telecon Tuesday, we finally broke down and decided we needed to do all the system nastiness to intercept free() and munmap() and the like for high speed interconnects so that we can do pinned page caching and not take the pinning performance hit on applicatio

[O-MPI devel] Fwd: Memory manager changes

2005-08-12 Thread Rich L. Graham
Brian, Sounds like I got off the call a bit too early ;-) Can we choose to use standard platform libraries, or are we pinning ourselves into a corner ? I.e., is this optional ? What sort of problems are we getting into playing with pre-load options ? I would be VERY careful her

Re: [O-MPI devel] Fwd: Memory manager changes

2005-08-12 Thread Brian Barrett
On Aug 12, 2005, at 9:43 PM, Rich L. Graham wrote: Sounds like I got off the call a bit too early ;-) Can we choose to use standard platform libraries, or are we pinning ourselves into a corner ? I.e., is this optional ? Yes - the code is all built around trying to use the sta

Re: [O-MPI devel] Fwd: Memory manager changes

2005-08-12 Thread Rich L. Graham
Sound reasonable - I am for being able to turn on optional things that will improve performance... Thanks, Rich On Aug 12, 2005, at 9:14 PM, Brian Barrett wrote: On Aug 12, 2005, at 9:43 PM, Rich L. Graham wrote: Sounds like I got off the call a bit too early ;-) Can we choose to