[PATCH] [RFC] malloc: Reduce worst-case behaviour with madvise and refault overhead
Florian Weimer
fweimer@redhat.com
Tue Feb 10 12:30:00 GMT 2015
On 02/09/2015 09:52 PM, Carlos O'Donell wrote:
> On 02/09/2015 09:06 AM, Mel Gorman wrote:
>> while (data_to_process) {
>> buf = malloc(large_size);
>> do_stuff();
>> free(buf);
>> }
>
> Why isn't the fix to change the application to hoist the
> malloc out of the loop?
For a lot of C++ code, this would require replacing global operator new
with a pool allocator. We do not want programmers to do that, for
various reasons (loss of tooling, our limited malloc hardening, etc.).
--
Florian Weimer / Red Hat Product Security
More information about the Libc-alpha
mailing list