From: Wilco Dijkstra <Wilco.Dijkstra@arm.com>
To: Carlos O'Donell <carlos@redhat.com>,
'GNU C Library' <libc-alpha@sourceware.org>
Subject: Re: [PATCH] Improve performance of libc locks
Date: Mon, 15 Aug 2022 17:35:35 +0000 [thread overview]
Message-ID: <AM5PR0801MB166803899DE39D98B9E0D13683689@AM5PR0801MB1668.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <d3b3d63a-d3fe-f9d3-c31a-aaf91a520b4c@redhat.com>
Hi Carlos,
> This impacts all architectures.
That was the goal indeed - we should add single-threaded optimizations in a
generic way.
> If we don't have a benchmark that shows this specific base of ST vs MT and
> internal __libc_lock_lock-locks then we should add one. Improving the internal
> locking for our algorithms is always going to be a point of interest for IHVs.
I can easily wrap my rand() microbench in json and add it to the benchtests.
I think it would be harder to do more tests on internal locks/headers since they
are not easily usable from benchtest infrastructure (just including libc-lock.h
results in lots of errors...).
Cheers,
Wilco
next prev parent reply other threads:[~2022-08-15 17:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-11 16:22 Wilco Dijkstra
2022-08-15 14:07 ` Carlos O'Donell
2022-08-15 17:35 ` Wilco Dijkstra [this message]
2022-08-16 7:26 ` Noah Goldstein
2022-11-15 20:17 ` Cristian Rodríguez
2022-12-09 14:10 ` Wilco Dijkstra
2023-11-23 17:16 ` Cristian Rodríguez
2023-11-23 18:17 ` Florian Weimer
2023-11-24 13:47 ` Wilco Dijkstra
2023-11-24 16:29 ` Carlos O'Donell
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=AM5PR0801MB166803899DE39D98B9E0D13683689@AM5PR0801MB1668.eurprd08.prod.outlook.com \
--to=wilco.dijkstra@arm.com \
--cc=carlos@redhat.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).