From: Sergey Bugaev via Libc-alpha <libc-alpha@sourceware.org>
To: Samuel Thibault <samuel.thibault@gnu.org>
Cc: bug-hurd <bug-hurd@gnu.org>, libc-alpha@sourceware.org
Subject: Re: [PATCH htl v3 2/5] htl: Move thread table to ld.so
Date: Wed, 15 Sep 2021 18:13:15 +0300 [thread overview]
Message-ID: <CAN9u=HcxunQAVJ8kHajjsJY=3TWg-3bgvxFsCP+4k_yf+EbFNg@mail.gmail.com> (raw)
In-Reply-To: <20210915143427.4djiwiucrgz65pru@begin>
On Wed, Sep 15, 2021 at 5:34 PM Samuel Thibault <samuel.thibault@gnu.org> wrote:
> so it's probably not
> worth spending time on making a separate __libc_rwlock implementation,
> and rather spend it on making pthread_rwlock use gsync, like was done
> for pthread_mutex and sem
Oh, it currently doesn't? That's horrifying. Then I'll look into that next.
Sergey
P.S. There's this other thing that is way more urgent than either
eliminating gsync_wake () calls or optimizing rwlocks. I sent you an
email a week ago. Please take a look.
next prev parent reply other threads:[~2021-09-15 15:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-07 13:33 [PATCH htl v3 0/5] Rewrite THREAD_GSCOPE Sergey Bugaev via Libc-alpha
2021-09-07 13:33 ` [PATCH htl v3 1/5] elf: Replace most uses of THREAD_GSCOPE_IN_TCB Sergey Bugaev via Libc-alpha
2021-09-14 23:30 ` Samuel Thibault via Libc-alpha
2021-09-07 13:33 ` [PATCH htl v3 2/5] htl: Move thread table to ld.so Sergey Bugaev via Libc-alpha
2021-09-14 23:27 ` Samuel Thibault via Libc-alpha
2021-09-15 14:14 ` Sergey Bugaev via Libc-alpha
2021-09-15 14:34 ` Samuel Thibault via Libc-alpha
2021-09-15 14:35 ` Samuel Thibault via Libc-alpha
2021-09-15 15:13 ` Sergey Bugaev via Libc-alpha [this message]
2021-09-15 15:16 ` Samuel Thibault via Libc-alpha
2021-09-07 13:33 ` [PATCH htl v3 3/5] htl: Reimplement GSCOPE Sergey Bugaev via Libc-alpha
2021-09-14 23:28 ` Samuel Thibault via Libc-alpha
2021-09-07 13:33 ` [PATCH htl v3 4/5] elf: Remove THREAD_GSCOPE_IN_TCB Sergey Bugaev via Libc-alpha
2021-09-14 23:29 ` Samuel Thibault via Libc-alpha
2021-09-07 13:33 ` [PATCH htl v3 5/5] testrun.sh: Add support for --tool=rpctrace Sergey Bugaev via Libc-alpha
2021-09-08 6:57 ` Florian Weimer via Libc-alpha
2021-09-09 23:25 ` Samuel Thibault via Libc-alpha
2021-09-07 17:05 ` [PATCH htl v3 0/5] Rewrite THREAD_GSCOPE Adhemerval Zanella via Libc-alpha
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAN9u=HcxunQAVJ8kHajjsJY=3TWg-3bgvxFsCP+4k_yf+EbFNg@mail.gmail.com' \
--to=libc-alpha@sourceware.org \
--cc=bug-hurd@gnu.org \
--cc=bugaevc@gmail.com \
--cc=samuel.thibault@gnu.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).