[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <2649c14b-bee1-f94c-4e59-769a096af391@gmail.com>
Date: Fri, 24 Jun 2016 12:00:05 +0200
From: "Michael Kerrisk (man-pages)" <mtk.manpages@...il.com>
To: Thomas Gleixner <tglx@...utronix.de>
Cc: mtk.manpages@...il.com, Darren Hart <dvhart@...radead.org>,
Matthieu CASTET <matthieu.castet@...rot.com>,
linux-kernel@...r.kernel.org, Darren Hart <dvhart@...ux.intel.com>,
Peter Zijlstra <peterz@...radead.org>,
Davidlohr Bueso <dave@...olabs.net>,
Eric Dumazet <dada1@...mosbay.com>
Subject: Re: futex: Allow FUTEX_CLOCK_REALTIME with FUTEX_WAIT op
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/
Powered by blists - more mailing lists