From: DJ Delorie <dj@redhat.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: Wilco.Dijkstra@arm.com, libc-alpha@sourceware.org
Subject: Re: [PATCH v6 3/4] Reduce CAS in malloc spinlocks
Date: Thu, 23 Feb 2023 15:07:27 -0500 [thread overview]
Message-ID: <xn1qmg87sw.fsf@greed.delorie.com> (raw)
In-Reply-To: <CAMe9rOrR==zMUVYcCS3p4hL1GdTLrSsXoX4-3iJZqrvcq8M0iw@mail.gmail.com>
"H.J. Lu" <hjl.tools@gmail.com> writes:
> I didn't pursue it further since I couldn't show how much it would
> improve performance.
Yeah, that's one of the big problems with malloc is benchmarking - it's
easy to write a bad benchmark, and hard to capture what real-world
applications are doing. And any benchmark complex enough to be relevent
in this case would be chaotic enough to lose the tiny changes in the
noise.
next prev parent reply other threads:[~2023-02-23 20:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-23 18:27 Wilco Dijkstra
2023-02-23 19:53 ` H.J. Lu
2023-02-23 20:07 ` DJ Delorie [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-11-15 13:01 Wilco Dijkstra
2021-11-11 16:24 [PATCH v6 0/4] Optimize CAS [BZ #28537] H.J. Lu
2021-11-11 16:24 ` [PATCH v6 3/4] Reduce CAS in malloc spinlocks H.J. Lu
2023-02-23 5:48 ` 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=xn1qmg87sw.fsf@greed.delorie.com \
--to=dj@redhat.com \
--cc=Wilco.Dijkstra@arm.com \
--cc=hjl.tools@gmail.com \
--cc=libc-alpha@sourceware.org \
/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).