apr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Paul Querna <p...@querna.org>
Subject Re: [PATCH] pools always use malloc
Date Wed, 25 Mar 2009 14:48:23 GMT
On Wed, Mar 25, 2009 at 3:44 PM, Mladen Turk <mturk@apache.org> wrote:
> Paul Querna wrote:
>>
>> On Wed, Mar 25, 2009 at 3:39 PM, Mladen Turk <mturk@apache.org> wrote:
>>>
>>> Paul Querna wrote:
>>>>
>>>> There have been various discussions on list in the past about the
>>>> problems with pools, and that newer malloc implementations really are
>>>> better at it han we can ever be. (jemalloc for example
>>>> <http://people.freebsd.org/~jasone/jemalloc/bsdcan2006/jemalloc.pdf>).
>>>>
>>>> Patch:
>>>> <http://people.apache.org/~pquerna/marvelous-malloc.patch>
>>>>
>>>> - palloc now used malloc underneath.
>>>> - we keep a list of malloc'ed adrresses, in a new list object, and
>>>> free them on clear/destroy
>>>> - unmanaged/core pool APIs removed.
>>>>
>>>> I'd like to just put this into APR-2 trunk asap, and then figure out
>>>> how to unify the pool debug code with these changes.
>>>>
>>>> Thoughts?
>>>>
>>> Why did you remove the unmanaged pool?
>>
>> because when we are using malloc/free, they shouldn't be needed?
>>
>
> That's not its purpose.
> It's purpose is to detach from global pool.

Yes, but the next step is to remove the global pool :)

Mime
View raw message