From: "Cristian Rodríguez" <cristian@rodriguez.im>
To: Wilco Dijkstra <Wilco.Dijkstra@arm.com>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH 2/2] Add single-threaded fast path to rand()
Date: Mon, 18 Mar 2024 16:24:52 -0300 [thread overview]
Message-ID: <CAPBLoAcyGR5N4-rt+iZFuKMghGSvYUqGSw1T6aiKyRph=hhFxQ@mail.gmail.com> (raw)
In-Reply-To: <PAWPR08MB898203ABD80D81B91E5398B4832D2@PAWPR08MB8982.eurprd08.prod.outlook.com>
On Mon, Mar 18, 2024 at 12:21 PM Wilco Dijkstra <Wilco.Dijkstra@arm.com> wrote:
>
> Improve performance of rand() and __random() by adding a single-threaded fast
> path. Bench-random-lock shows about 5x speedup on Neoverse V1.
>
> OK for commit?
So the generalized lock-omitting code in __libc_lock_lock didn't
flew.. what a new fast path macro function like (sorry I suck at
naming things) __libc_maybe_lock_lock that only locks if not single
thread ?
next prev parent reply other threads:[~2024-03-18 19:25 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-18 15:20 Wilco Dijkstra
2024-03-18 19:24 ` Cristian Rodríguez [this message]
2024-03-19 15:44 ` Wilco Dijkstra
2024-03-20 12:31 ` Adhemerval Zanella Netto
2024-03-20 14:18 ` Cristian Rodríguez
2024-03-20 14:27 ` Adhemerval Zanella Netto
2024-03-21 7:39 ` Florian Weimer
2024-03-21 13:33 ` Cristian Rodríguez
2024-03-21 14:35 ` Mathieu Desnoyers
2024-03-21 15:07 ` Szabolcs Nagy
2024-03-21 15:18 ` Wilco Dijkstra
2024-03-21 15:53 ` Adhemerval Zanella Netto
2024-03-22 14:27 ` Zack Weinberg
2024-03-22 14:46 ` Adhemerval Zanella Netto
2024-03-22 15:30 ` Zack Weinberg
2024-03-22 18:05 ` Adhemerval Zanella Netto
2024-03-22 19:47 ` Mathieu Desnoyers
2024-03-22 22:54 ` Cristian Rodríguez
2024-03-23 14:01 ` Zack Weinberg
2024-03-23 15:23 ` Mathieu Desnoyers
2024-03-25 14:09 ` Mathieu Desnoyers
2024-03-25 17:52 ` Adhemerval Zanella Netto
2024-03-24 0:59 ` Cristian Rodríguez
2024-03-25 6:44 ` Florian Weimer
2024-03-20 14:28 ` Wilco Dijkstra
2024-03-20 14:40 ` Xi Ruoyao
-- strict thread matches above, loose matches on Subject: below --
2023-11-28 17:37 Wilco Dijkstra
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='CAPBLoAcyGR5N4-rt+iZFuKMghGSvYUqGSw1T6aiKyRph=hhFxQ@mail.gmail.com' \
--to=cristian@rodriguez.im \
--cc=Wilco.Dijkstra@arm.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).