Re: [OMPI devel] RFC: make mpi_leave_pinned=1 the default

2008-07-07 Thread Jeff Squyres
On Jul 6, 2008, at 1:28 PM, Patrick Geoffray wrote: WHAT: make mpi_leave_pinned=1 by default when a BTL is used that would benefit from it (when possible; 0 when not, obviously) The probable reason registration cache (aka leave_pinned) is disabled by default is that it may be unsafe. Even i

Re: [OMPI devel] RFC: make mpi_leave_pinned=1 the default

2008-07-06 Thread Patrick Geoffray
Jeff Squyres wrote: WHAT: make mpi_leave_pinned=1 by default when a BTL is used that would benefit from it (when possible; 0 when not, obviously) Comments? The probable reason registration cache (aka leave_pinned) is disabled by default is that it may be unsafe. Even if you use mallocopt to

Re: [OMPI devel] RFC: make mpi_leave_pinned=1 the default

2008-07-03 Thread Torsten Hoefler
On Thu, Jul 03, 2008 at 05:56:52AM -0700, Jeff Squyres wrote: > - I know that leave_pinned is frequently meaningless to real apps > (although Torsten likes to argue otherwise -- and he's got at least > some real-world data points that show otherwise :-) ). I don't want to argue otherwise based

Re: [OMPI devel] RFC: make mpi_leave_pinned=1 the default

2008-07-03 Thread Brian W. Barrett
As long as we don't go back to libptmalloc2 linked into libmpi, I don't have strong objections. Brian On Thu, 3 Jul 2008, Jeff Squyres wrote: WHAT: make mpi_leave_pinned=1 by default when a BTL is used that would benefit from it (when possible; 0 when not, obviously) WHY: Several reasons: