From: Thomas Gleixner <tglx@linutronix.de>
To: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
Cc: Darren Hart <dvhart@infradead.org>,
Matthieu CASTET <matthieu.castet@parrot.com>,
linux-kernel@vger.kernel.org,
Darren Hart <dvhart@linux.intel.com>,
Peter Zijlstra <peterz@infradead.org>,
Davidlohr Bueso <dave@stgolabs.net>,
Eric Dumazet <dada1@cosmosbay.com>
Subject: Re: futex: Allow FUTEX_CLOCK_REALTIME with FUTEX_WAIT op
Date: Wed, 6 Jul 2016 20:57:59 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.11.1607062055570.4083@nanos> (raw)
In-Reply-To: <f1dab560-41bb-9cc4-438f-0ade82c685fd@gmail.com>
On Thu, 23 Jun 2016, Michael Kerrisk (man-pages) wrote:
> On 06/23/2016 08:28 PM, Darren Hart wrote:
> > And as a follow-on, what is the reason for FUTEX_LOCK_PI only using
> > CLOCK_REALTIME? It seems reasonable to me that a user may want to wait a
> > specific amount of time, regardless of wall time.
>
> Yes, that's another weird inconsistency.
The reason is that phtread_mutex_timedlock() uses absolute timeouts based on
CLOCK_REALTIME. glibc folks asked to make that the default behaviour back then
when we added LOCK_PI.
Thanks,
tglx
next prev parent reply other threads:[~2016-07-06 19:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-20 14:26 futex: Allow FUTEX_CLOCK_REALTIME with FUTEX_WAIT op Matthieu CASTET
2016-06-23 4:48 ` Darren Hart
2016-06-23 7:18 ` Thomas Gleixner
2016-06-23 10:52 ` Michael Kerrisk (man-pages)
2016-06-23 13:40 ` Thomas Gleixner
2016-06-23 16:16 ` Darren Hart
2016-06-23 17:26 ` Thomas Gleixner
2016-06-23 18:28 ` Darren Hart
2016-06-23 18:41 ` Michael Kerrisk (man-pages)
2016-06-23 19:55 ` Darren Hart
2016-06-23 20:31 ` Darren Hart
[not found] ` <d8bcb621-012e-f34c-4cf9-2d09aa23a43c@gmail.com>
2016-06-24 9:52 ` Thomas Gleixner
2016-06-24 10:00 ` Michael Kerrisk (man-pages)
2016-07-06 18:57 ` Thomas Gleixner [this message]
2016-06-23 18:35 ` Michael Kerrisk (man-pages)
2016-06-23 19:53 ` Darren Hart
2016-06-24 8:13 ` Michael Kerrisk (man-pages)
2016-06-23 10:53 ` Michael Kerrisk (man-pages)
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=alpine.DEB.2.11.1607062055570.4083@nanos \
--to=tglx@linutronix.de \
--cc=dada1@cosmosbay.com \
--cc=dave@stgolabs.net \
--cc=dvhart@infradead.org \
--cc=dvhart@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matthieu.castet@parrot.com \
--cc=mtk.manpages@gmail.com \
--cc=peterz@infradead.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 NNTP newsgroup(s).