Re: [OMPI devel] Dynamically Turning On and Off Memory Manager of Open MPI at Runtime??

Hi Peter, Peter Wong wrote: Open MPI defines its own malloc (by default), so malloc of glibc is not called. But, without calling malloc of glibc, the allocator of libhugetlbfs to back text and dynamic data by large pages, e.g., 16MB pages on POWER systems, is not used. You could modify ptmall

Re: [OMPI devel] Dynamically Turning On and Off Memory Manager of Open MPI at Runtime??

On Mon, 10 Dec 2007, Peter Wong wrote: Open MPI defines its own malloc (by default), so malloc of glibc is not called. But, without calling malloc of glibc, the allocator of libhugetlbfs to back text and dynamic data by large pages, e.g., 16MB pages on POWER systems, is not used. Indeed, we ca

[OMPI devel] Dynamically Turning On and Off Memory Manager of Open MPI at Runtime??

Open MPI defines its own malloc (by default), so malloc of glibc is not called. But, without calling malloc of glibc, the allocator of libhugetlbfs to back text and dynamic data by large pages, e.g., 16MB pages on POWER systems, is not used. Indeed, we can build Open MPI with --with-memory-manag