From: Florian Weimer <fweimer@redhat.com>
To: Yann Droneaud <ydroneaud@opteya.com>
Cc: Adhemerval Zanella via Libc-alpha <libc-alpha@sourceware.org>,
Wangyang Guo <wangyang.guo@intel.com>
Subject: Re: [PATCH v2] nptl: Add backoff mechanism to spinlock loop
Date: Fri, 22 Apr 2022 15:32:33 +0200 [thread overview]
Message-ID: <87o80ts0pa.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <6d934a2c-8f89-50ca-11b8-e2eaeb046add@opteya.com> (Yann Droneaud's message of "Fri, 22 Apr 2022 15:30:22 +0200")
* Yann Droneaud:
> Le 12/04/2022 à 13:53, Florian Weimer via Libc-alpha a écrit :
>> * Adhemerval Zanella via Libc-alpha:
>>
>>> On 30/03/2022 14:07, Noah Goldstein wrote:
>>>> What would be the best init jitter for arch w/ only syscall timers? TID? Or
>>>> something else?
>>> We don't cached the TID anymore, so it would still generate syscalls.
>> We do have the TID for the running process in the TCB. We need it (or
>> something like it) for recursive locks.
>>
>> Maybe for this application, we should use some number of upper bits from
>> a per-thread linear consequential generator, initialized to a random
>> value at thread start?
> As each running threads has its own stack, thread' stack address can
> be used as a seed for such PRNG.
We would broadcast the stack address though, which is generally fround
upon.
Thanks,
Florian
next prev parent reply other threads:[~2022-04-22 13:32 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-28 8:47 Wangyang Guo
2022-03-28 16:41 ` Noah Goldstein
2022-03-30 11:44 ` Guo, Wangyang
2022-03-30 19:39 ` Noah Goldstein
2022-03-30 11:53 ` Adhemerval Zanella
2022-03-30 17:07 ` Noah Goldstein
2022-03-30 17:21 ` Adhemerval Zanella
2022-04-12 11:53 ` Florian Weimer
2022-04-22 13:30 ` Yann Droneaud
2022-04-22 13:32 ` Florian Weimer [this message]
2022-04-22 13:35 ` Cristian Rodríguez
2022-04-22 15:25 ` Noah Goldstein
2022-04-26 12:25 ` Florian Weimer
2022-04-26 12:42 ` Yann Droneaud
2022-05-04 2:50 ` [PATCH v3] " Wangyang Guo
2022-05-04 2:58 ` Wangyang Guo
2022-05-04 3:17 ` [PATCH v4] " Wangyang Guo
2022-05-05 1:56 ` H.J. Lu
2022-05-05 2:52 ` Noah Goldstein
2022-05-05 2:59 ` Guo, Wangyang
2022-05-05 22:44 ` H.J. Lu
2022-05-06 1:52 ` Guo, Wangyang
2022-05-06 1:50 ` [PATCH v5] " Wangyang Guo
2022-05-06 3:06 ` H.J. Lu
2022-09-11 20:29 ` Sunil Pandey
2022-09-14 1:26 ` Noah Goldstein
2022-09-29 0:12 ` Noah Goldstein
2022-09-30 13:18 ` FUCKETY FUCK FUCK, PLEASE REMOVE ME FROM THESE EMAILS Darren Tristano
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=87o80ts0pa.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=wangyang.guo@intel.com \
--cc=ydroneaud@opteya.com \
/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).