This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: The direction of malloc?
- From: Jeff Law <law at redhat dot com>
- To: "Carlos O'Donell" <carlos at redhat dot com>, GNU C Library <libc-alpha at sourceware dot org>, Roland McGrath <roland at hack dot frob dot com>, Andreas Jaeger <aj at suse dot com>, "Joseph S. Myers" <joseph at codesourcery dot com>, Andreas Schwab <schwab at suse dot de>, OndÅej BÃlka <neleai at seznam dot cz>, Siddhesh Poyarekar <siddhesh at redhat dot com>
- Date: Mon, 09 Dec 2013 22:52:56 -0700
- Subject: Re: The direction of malloc?
- Authentication-results: sourceware.org; auth=none
- References: <52A6A0DA dot 1080109 at redhat dot com>
On 12/09/13 22:04, Carlos O'Donell wrote:
We should accept these patches without the restrictions we previously
placed on the malloc implementation. We should use GNU formatting to
make the code match all of our other styles. In effect we should
own the copy of ptmalloc2 we started with and change it into the
implementation that we think our users need.
There was a time when those restrictions made some sense, I think that
time has long past.
I even encourage the discussion of providing alternate allocators
like jemalloc.
The one thing I was ping'd regularly about was the allocator from
thread-building-blocks. Being able to use that without playing silly
games would be useful.
The other thing that I've been asked about a few times would be to fix
the thread safety issues around the hooks, which IIRC requires some
redesign.
jeff