Ah. On Linux, --without-threads really doesn't gain you that much. The
default glibc is still thread safe, and there are only a couple small
parts of the code that use locks (like the OOB TCP). It's generally just
easier to leave threads enabled on Linux.
Brian
On Thu, 22 May 2008, Don Ker
Thanks Jeff. Thanks Brian.
I ran into this because I was specifically trying to configure with
"--disable-progress-threads --disable-mpi-threads" at which point I
figured, might as well turn off all threads so I added
"--without-threads" as well. But can't live without mpi_leave_pinned so
thr
On May 21, 2008, at 4:37 PM, Brian W. Barrett wrote:
ptmalloc2 is not *required* by the openib btl. But it is required on
Linux if you want to use the mpi_leave_pinned functionality. I see
one function call to __pthread_initialize in the ptmalloc2 code -- it
*looks* like it's a function of gli
On Wed, 21 May 2008, Jeff Squyres wrote:
On May 21, 2008, at 4:17 PM, Don Kerr wrote:
Just want to make sure what I think I see is true:
Linux build. openib btl requires ptmalloc2 and ptmalloc2 requires
posix
threads, is that correct?
ptmalloc2 is not *required* by the openib btl. But it
On May 21, 2008, at 4:17 PM, Don Kerr wrote:
Just want to make sure what I think I see is true:
Linux build. openib btl requires ptmalloc2 and ptmalloc2 requires
posix
threads, is that correct?
ptmalloc2 is not *required* by the openib btl. But it is required on
Linux if you want to us
