From: Wilco Dijkstra <Wilco.Dijkstra@arm.com>
To: "eggert@cs.ucla.edu" <eggert@cs.ucla.edu>,
"Ondřej Bílka" <neleai@seznam.cz>
Cc: nd <nd@arm.com>, Carlos O'Donell <carlos@redhat.com>,
"libc-alpha@sourceware.org" <libc-alpha@sourceware.org>
Subject: Re: Possible inline malloc alternatives: bitmap
Date: Sun, 04 Mar 2018 14:07:00 -0000 [thread overview]
Message-ID: <DB6PR0801MB2053C3D9CB3268A349BE72B783DB0@DB6PR0801MB2053.eurprd08.prod.outlook.com> (raw)
Paul Eggert wrote:
> You can freely read an older NightWatch paper here:
>
> Although NightWatch's source code is freely readable (it's on GitHub), it does not specify a software licence so I have not read it and don't recommend that you read it.
> > One problem is that it merges several different issues.
>
> Yes, a problem common to many systems papers.
Indeed, it is not relevant to the issues we are having with GLIBC malloc. The paper is about
system wide cache partitioning which is very system specific and between processes.
> I didn't quite follow your profiling proposals. As near as I can make out you'd like to log calls to malloc, free, etc. But for good results don't you also need to log memory accesses? Otherwise how will you know which objects are hot?
I don't believe it is feasible to profile malloc more accurately, but neither is it necessary
for a quick evaluation of malloc improvements like (de)allocation performance and
fragmentation reduction. You always need to run the original benchmark to prove the
gains are real.
Wilco
next reply other threads:[~2018-03-04 14:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-04 14:07 Wilco Dijkstra [this message]
2018-03-05 18:57 ` Carlos O'Donell
-- strict thread matches above, loose matches on Subject: below --
2018-03-02 5:54 Ondřej Bílka
2018-03-02 5:54 ` Ondřej Bílka
2018-03-02 18:20 ` DJ Delorie
2018-03-02 16:28 ` Carlos O'Donell
2018-03-02 20:21 ` Paul Eggert
2018-03-03 12:56 ` Ondřej Bílka
2018-03-03 20:24 ` Paul Eggert
2018-03-03 23:37 ` Carlos O'Donell
2018-03-03 23:40 ` Carlos O'Donell
2018-03-04 15:51 ` Ondřej Bílka
2018-03-02 23:00 ` Ondřej Bílka
2018-03-05 20:32 ` DJ Delorie
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=DB6PR0801MB2053C3D9CB3268A349BE72B783DB0@DB6PR0801MB2053.eurprd08.prod.outlook.com \
--to=wilco.dijkstra@arm.com \
--cc=carlos@redhat.com \
--cc=eggert@cs.ucla.edu \
--cc=libc-alpha@sourceware.org \
--cc=nd@arm.com \
--cc=neleai@seznam.cz \
/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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).