[PATCH] malloc: Move mmap code out of __libc_free hotpath

DJ Delorie dj@redhat.com
Tue Mar 25 03:59:55 GMT 2025


Wilco Dijkstra <Wilco.Dijkstra@arm.com> writes:
>> ... the rest of this looks ok, but it leaves _libc_free and _int_free as
>> being very small functions.  Do we need them?  Or are we relying on the
>> inlining to make them efficient?
>
> No we don't need them - the next step is move _int_free-* into __libc_free,
> simplify the code and use a similar tailcall approach as __libc_malloc. This
> gives similar speedups as malloc!

Does this imply that the tcache stuff will only live in __libc_free and
nothing else will populate tcache from internally?



More information about the Libc-alpha mailing list