From: Arjan van de Ven <arjan@linux.intel.com>
To: "H.J. Lu" <hjl.tools@gmail.com>,
Noah Goldstein <goldstein.w.n@gmail.com>
Cc: GNU C Library <libc-alpha@sourceware.org>,
Florian Weimer <fweimer@redhat.com>,
Oleh Derevenko <oleh.derevenko@gmail.com>,
Andreas Schwab <schwab@linux-m68k.org>,
"Paul A . Clarke" <pc@us.ibm.com>
Subject: Re: [PATCH v6 1/4] Add LLL_MUTEX_READ_LOCK [BZ #28537]
Date: Wed, 17 Nov 2021 17:16:41 -0800 [thread overview]
Message-ID: <924a80cd-202c-99e9-a2d9-1aeda2235b83@linux.intel.com> (raw)
In-Reply-To: <CAMe9rOpE1+1zqtA4xqJNy-RK03jXNzv-JnYSJFtGmtqSa2QqQQ@mail.gmail.com>
On 11/17/2021 4:31 PM, H.J. Lu wrote:
>> Yes, but the loop will be able to run `max_cnt` iterations much faster now.
>> Just wondering if the value needs to be re-tuned. Not that is necessarily needs
>> to be.
> Maybe if we can find some data to show for.
>
wondering when this was last tuned.. I assume todays CPUs and CPUs from, say, 5 or 10 years ago
have an order of magnitude different performance in this regard....
if there wasn't a need to retune during that, maybe this value is so robust that it doesn't need
retuning.
or maybe it's time to retune this in general sometime soon after this patch goes in ;)
next prev parent reply other threads:[~2021-11-18 1:17 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-11 16:24 [PATCH v6 0/4] Optimize CAS " H.J. Lu
2021-11-11 16:24 ` [PATCH v6 1/4] Add LLL_MUTEX_READ_LOCK " H.J. Lu
2021-11-12 17:23 ` Szabolcs Nagy
2021-11-17 2:24 ` Noah Goldstein
2021-11-17 23:54 ` H.J. Lu
2021-11-18 0:03 ` Noah Goldstein
2021-11-18 0:31 ` H.J. Lu
2021-11-18 1:16 ` Arjan van de Ven [this message]
2022-09-11 20:19 ` Sunil Pandey
2022-09-29 0:10 ` Noah Goldstein
2021-11-11 16:24 ` [PATCH v6 2/4] Avoid extra load with CAS in __pthread_mutex_lock_full " H.J. Lu
2021-11-12 16:31 ` Szabolcs Nagy
2021-11-12 18:50 ` Andreas Schwab
2022-09-11 20:16 ` Sunil Pandey
2022-09-29 0:10 ` Noah Goldstein
2021-11-11 16:24 ` [PATCH v6 3/4] Reduce CAS in malloc spinlocks H.J. Lu
2023-02-23 5:48 ` DJ Delorie
2021-11-11 16:24 ` [PATCH v6 4/4] Avoid extra load with CAS in __pthread_mutex_clocklock_common [BZ #28537] H.J. Lu
2021-11-12 16:32 ` Szabolcs Nagy
2021-11-12 18:51 ` Andreas Schwab
2022-09-11 20:12 ` Sunil Pandey
2022-09-11 20:15 ` Arjan van de Ven
2022-09-11 21:26 ` Florian Weimer
2022-09-29 0:09 ` Noah Goldstein
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=924a80cd-202c-99e9-a2d9-1aeda2235b83@linux.intel.com \
--to=arjan@linux.intel.com \
--cc=fweimer@redhat.com \
--cc=goldstein.w.n@gmail.com \
--cc=hjl.tools@gmail.com \
--cc=libc-alpha@sourceware.org \
--cc=oleh.derevenko@gmail.com \
--cc=pc@us.ibm.com \
--cc=schwab@linux-m68k.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).