Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 30 Aug 2018 13:16:27 -0500
From: "A. Wilcox" <>
Subject: Re: malloc implementation survey: omalloc

On 07/30/18 20:44, Rich Felker wrote:
> One thing that would probably be really useful is empirical data on
> what range of sizes "need to be fast" for bloated OO stuff that does
> rapid malloc/free cycles. Conceptually it should only be small sizes,
> assuming the whole allocated space is actually used, since beyond a
> certain size, actual use of the allocated memory (loads/stores) will
> dominate the time spent allocating and freeing it, but the cutoff
> isn't clear.
> Rich

I can probably instrument the malloc() patterns of Firefox and Plasma
Shell.  Can you provide me the desired format?

I would probably simply change musl to print "a:%lld\n" to stderr for
each allocation, and then I could turn it into better formatted data.


A. Wilcox (awilfox)
Project Lead, Adélie Linux

Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.