Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752203AbbG0LKz (ORCPT ); Mon, 27 Jul 2015 07:10:55 -0400 Received: from mail-wi0-f176.google.com ([209.85.212.176]:34389 "EHLO mail-wi0-f176.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751125AbbG0LKw (ORCPT ); Mon, 27 Jul 2015 07:10:52 -0400 Message-ID: <55B611B3.7030005@gmail.com> Date: Mon, 27 Jul 2015 13:10:43 +0200 From: "Michael Kerrisk (man-pages)" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: Davidlohr Bueso , Peter Zijlstra CC: mtk.manpages@gmail.com, Thomas Gleixner , Darren Hart , "Carlos O'Donell" , Ingo Molnar , Jakub Jelinek , "linux-man@vger.kernel.org" , lkml , Arnd Bergmann , Steven Rostedt , Linux API , Torvald Riegel , Roland McGrath , Darren Hart , Anton Blanchard , Eric Dumazet , bill o gallmeister , Jan Kiszka , Daniel Wagner , Rich Felker , Andy Lutomirski , bert hubert , Rusty Russell , Heinrich Schuchardt Subject: Re: Revised futex(2) man page for review References: <55166C01.7000803@gmail.com> <20150328114725.GJ27490@worktop.programming.kicks-ass.net> <1427813146.20009.2.camel@stgolabs.net> In-Reply-To: <1427813146.20009.2.camel@stgolabs.net> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1484 Lines: 39 Hi David, On 03/31/2015 04:45 PM, Davidlohr Bueso wrote: > On Sat, 2015-03-28 at 12:47 +0100, Peter Zijlstra wrote: > >> The condition is represented by the futex word, which is an address in >> memory supplied to the futex() system call, and the value at this mem‐ >> ory location. (While the virtual addresses for the same memory in sep‐ >> arate processes may not be equal, the kernel maps them internally so >> that the same memory mapped in different locations will correspond for >> futex() calls.) >> >> 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 > > Given the use of "word", you should probably state right away that > futexes are only 32bit. So, I made the opening sentence here: The condition is represented by the futex word, which is an address in memory supplied to the futex() system call, and the 32-bit value at this memory location. Okay? Cheers, Michael -- Michael Kerrisk Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/ Linux/UNIX System Programming Training: http://man7.org/training/ -- 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/