From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751137AbbCaDbq (ORCPT ); Mon, 30 Mar 2015 23:31:46 -0400 Received: from ozlabs.org ([103.22.144.67]:37492 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753162AbbCaDba (ORCPT ); Mon, 30 Mar 2015 23:31:30 -0400 From: Rusty Russell To: "Michael Kerrisk \(man-pages\)" , Thomas Gleixner , Darren Hart Cc: mtk.manpages@gmail.com, "Carlos O'Donell" , Darren Hart , Ingo Molnar , Jakub Jelinek , "linux-man\@vger.kernel.org" , lkml , Davidlohr Bueso , Arnd Bergmann , Steven Rostedt , Peter Zijlstra , Linux API , Torvald Riegel , Roland McGrath , Darren Hart , Anton Blanchard , Peter Zijlstra , Eric Dumazet , bill o gallmeister , Jan Kiszka , Daniel Wagner , Rich Felker , Andy Lutomirski , bert hubert , Heinrich Schuchardt Subject: Re: Revised futex(2) man page for review In-Reply-To: <55166C01.7000803@gmail.com> References: <55166C01.7000803@gmail.com> User-Agent: Notmuch/0.17 (http://notmuchmail.org) Emacs/24.3.1 (x86_64-pc-linux-gnu) Date: Tue, 31 Mar 2015 12:18:41 +1030 Message-ID: <871tk6os1y.fsf@rustcorp.com.au> MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org "Michael Kerrisk (man-pages)" writes: > When executing a futex operation that requests to block a thread, > the kernel will only block if the futex word has the value that the > calling thread supplied as expected value. > The load from the futex word, the comparison with > the expected value, > and the actual blocking will happen atomically and totally > ordered with respect to concurrently executing futex operations > on the same futex word, > such as operations that wake threads blocked on this futex word. > Thus, the futex word is used to connect the synchronization in user spac Missing 'e' in "space". > .\" FIXME Please confirm that the following is correct: > No guarantee is provided about which waiters are awoken > (e.g., a waiter with a higher scheduling priority is not guaranteed > to be awoken in preference to a waiter with a lower priority). This is true. I didn't read the rest, as that stuff was all written by others. Documenting them is pretty heroic; good job! Thanks, Rusty.