mailing list of musl libc
 help / color / mirror / code / Atom feed
From: "A. Wilcox" <awilfox@adelielinux.org>
To: musl@lists.openwall.com
Subject: Re: malloc implementation survey: omalloc
Date: Thu, 30 Aug 2018 13:16:27 -0500	[thread overview]
Message-ID: <07695a41-d027-a585-fa2f-5edae4d23af4@adelielinux.org> (raw)
In-Reply-To: <20180731014407.GE1392@brightrain.aerifal.cx>


[-- Attachment #1.1: Type: text/plain, Size: 867 bytes --]

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.

Best,
--arw


-- 
A. Wilcox (awilfox)
Project Lead, Adélie Linux
http://adelielinux.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2018-08-30 18:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-29 19:26 Markus Wichmann
2018-07-30 15:09 ` Christopher Friedt
2018-07-30 19:14   ` Christopher Friedt
2018-07-30 19:22     ` Christopher Friedt
2018-07-30 19:34       ` Christopher Friedt
2018-07-31  7:49   ` Markus Wichmann
2018-07-31 14:25     ` Rich Felker
2018-07-31 14:49     ` Christopher Friedt
2018-07-31  0:47 ` Rich Felker
2018-07-31  1:44   ` Rich Felker
2018-08-30 18:16     ` A. Wilcox [this message]
2018-08-30 18:46       ` Rich Felker

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=07695a41-d027-a585-fa2f-5edae4d23af4@adelielinux.org \
    --to=awilfox@adelielinux.org \
    --cc=musl@lists.openwall.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).