From: Florian Weimer <fweimer@redhat.com>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH v2 3/4] linux: Move funlockfile/_IO_funlockfile into libc
Date: Mon, 10 May 2021 19:33:05 +0200 [thread overview]
Message-ID: <87bl9i7aum.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <20210510170426.2533768-3-adhemerval.zanella@linaro.org> (Adhemerval Zanella's message of "Mon, 10 May 2021 14:04:25 -0300")
* Adhemerval Zanella:
> The nptl version is used as default, since now with symbol always
> present the single-thread optimization is tricky.
>
> Hurd is not change, it is used it own lock scheme (which call
> _cthreads_funlockfile).
>
> Checked on x86_64-linux-gnu.
Looks fine to me.
Thanks,
Florian
next prev parent reply other threads:[~2021-05-10 17:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-10 17:04 [PATCH v2 1/4] linux: Move flockfile/_IO_flockfile " Adhemerval Zanella
2021-05-10 17:04 ` [PATCH v2 2/4] linux: Move ftrylockfile/_IO_ftrylockfile " Adhemerval Zanella
2021-05-10 17:32 ` Florian Weimer
2021-05-10 17:04 ` [PATCH v2 3/4] linux: Move funlockfile/_IO_funlockfile " Adhemerval Zanella
2021-05-10 17:33 ` Florian Weimer [this message]
2021-05-10 17:04 ` [PATCH v2 4/4] libio: Fix race access to _IO_FLAGS2_NEED_LOCK Adhemerval Zanella
2021-05-10 17:46 ` Florian Weimer
2021-05-10 19:11 ` Adhemerval Zanella
2021-05-10 19:18 ` Florian Weimer
2021-05-10 19:25 ` Florian Weimer
2021-05-10 19:25 ` Adhemerval Zanella
2021-05-10 19:33 ` Florian Weimer
2021-05-10 21:42 ` Adhemerval Zanella
2021-05-10 21:46 ` Adhemerval Zanella
2021-05-11 10:06 ` Florian Weimer
2021-05-11 12:29 ` Adhemerval Zanella
2021-05-10 17:30 ` [PATCH v2 1/4] linux: Move flockfile/_IO_flockfile into libc Florian Weimer
2021-05-10 19:27 ` Adhemerval Zanella
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=87bl9i7aum.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=adhemerval.zanella@linaro.org \
--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).