On Wed, 4 Jun 2008, Paul H. Hargrove wrote:
Brian states
This will allow users to turn ptmalloc2 support on/off at application
link time instead of MPI compile time.
Where I assume "MPI compile time" means when the MPI *implementation* is
compiled.
Correct.
So what about LD_PRELOAD? Can
Brian states
This will
allow users to turn ptmalloc2 support on/off at application link time
instead of MPI compile time.
Where I assume "MPI compile time" means when the MPI *implementation* is
compiled.
So what about LD_PRELOAD? Can the user defer the decision to use
ptmalloc until app
Sounds good to me. Thanks Brian!
On Jun 3, 2008, at 12:04 PM, Brian W. Barrett wrote:
Hi all -
Sorry this is so late, but it took a couple of iterations with a
couple of
people to get right from a technology standpoint. All mistakes in
this
proposal are my fault.
What: Fix the ptmallo
Hi all -
Sorry this is so late, but it took a couple of iterations with a couple of
people to get right from a technology standpoint. All mistakes in this
proposal are my fault.
What: Fix the ptmalloc2 problem
How: Remove it from the default path
When: This weekend? For the 1.3 branch
The pro
Hi folks
I'm posting this here for want of any other obvious place. As always,
if it should be redirected please let me know.
Questions: How much does using the MPI wrappers influence the memory
management at runtime? What has changed in this regard from 1.2.3 to
1.2.4?
The reason I ask is
