Date: Mon, 27 Apr 2015 22:37:05 +0200
From: Pavel Machek <pavel@ucw.cz>
To: Peter Zijlstra <peterz@infradead.org>
Cc: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>,
        Thomas Gleixner <tglx@linutronix.de>,
        Darren Hart <dvhart@linux.intel.com>,
        "Carlos O'Donell" <carlos@redhat.com>, Ingo Molnar <mingo@elte.hu>,
        Jakub Jelinek <jakub@redhat.com>,
        "linux-man@vger.kernel.org" <linux-man@vger.kernel.org>,
        lkml <linux-kernel@vger.kernel.org>,
        Davidlohr Bueso <dave@stgolabs.net>, Arnd Bergmann <arnd@arndb.de>,
        Steven Rostedt <rostedt@goodmis.org>,
        Linux API <linux-api@vger.kernel.org>,
        Torvald Riegel <triegel@redhat.com>,
        Roland McGrath <roland@hack.frob.com>,
        Darren Hart <dvhart@infradead.org>, Anton Blanchard <anton@samba.org>,
        Eric Dumazet <edumazet@google.com>,
        bill o gallmeister <bgallmeister@gmail.com>,
        Jan Kiszka <jan.kiszka@siemens.com>, Daniel Wagner <wagi@monom.org>,
        Rich Felker <dalias@libc.org>, Andy Lutomirski <luto@amacapital.net>,
        bert hubert <bert.hubert@netherlabs.nl>,
        Rusty Russell <rusty@rustcorp.com.au>,
        Heinrich Schuchardt <xypron.glpk@gmx.de>
Subject: Re: Revised futex(2) man page for review
Message-ID: <20150427203705.GE29351@xo-6d-61-c0.localdomain>
References: <55166C01.7000803@gmail.com>
 <20150328114725.GJ27490@worktop.programming.kicks-ass.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20150328114725.GJ27490@worktop.programming.kicks-ass.net>
User-Agent: Mutt/1.5.21 (2010-09-15)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1755
Lines: 45

Hi!

>               The FUTEX_WAIT_OP operation is equivalent to execute the follow???
>               ing  code  atomically  and totally ordered with respect to other
>               futex operations on any of the two supplied futex words:

"to executing"?

>               The  operation  and  comparison  that  are  to  be performed are
>               encoded in the bits of  the  argument  val3.   Pictorially,  the
>               encoding is:
> 
>                       +---+---+-----------+-----------+
>                       |op |cmp|   oparg   |  cmparg   |
>                       +---+---+-----------+-----------+
>                         4   4       12          12    <== # of bits
> 

:-)

> RETURN VALUE
>        In the event of an error, all operations return -1  and  set  errno  to
>        indicate  the  cause of the error.  The return value on success depends
>        on the operation, as described in the following list:

Did you say (at the begining) that there is no glibc wrapper?

>        EINVAL The operation in futex_op is one of those that employs  a  time???
>               out,  but  the supplied timeout argument was invalid (tv_sec was
>               less than zero, or tv_nsec was not less than 1000,000,000).

1,000...?

> NOTES
>        Glibc does not provide a wrapper for this system call;  call  it  using
>        syscall(2).

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/