From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: mtk.manpages@gmail.com, 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: Fri, 24 Jun 2016 12:00:05 +0200 [thread overview]
Message-ID: <2649c14b-bee1-f94c-4e59-769a096af391@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.11.1606241151500.5839@nanos>
On 06/24/2016 11:52 AM, Thomas Gleixner wrote:
> On Fri, 24 Jun 2016, Michael Kerrisk (man-pages) wrote:
>> By the way, I just realized something that wasn't initially obvious
>> to me, and documented it in the futex(2) man page:
>>
>> Note: for FUTEX_WAIT, timeout is interpreted as a
>> relative value. This differs from other futex oper‐
>> ations, where timeout is interpreted as an absolute
>> value. To obtain the equivalent of FUTEX_WAIT with
>> an absolute timeout, employ FUTEX_WAIT_BITSET with
>> val3 specified as FUTEX_BITSET_MATCH_ANY.
>>
>> Okay?
>
> Yes.
Thanks, Thomas.
Cheers,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
next prev parent reply other threads:[~2016-06-24 10: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) [this message]
2016-07-06 18:57 ` Thomas Gleixner
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=2649c14b-bee1-f94c-4e59-769a096af391@gmail.com \
--to=mtk.manpages@gmail.com \
--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=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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).