Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1946668AbbHHG4R (ORCPT ); Sat, 8 Aug 2015 02:56:17 -0400 Received: from mail-wi0-f174.google.com ([209.85.212.174]:37829 "EHLO mail-wi0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1946262AbbHHG4Q (ORCPT ); Sat, 8 Aug 2015 02:56:16 -0400 Message-ID: <55C5A802.7050602@gmail.com> Date: Sat, 08 Aug 2015 08:56:02 +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: Thomas Gleixner , Peter Zijlstra CC: mtk.manpages@gmail.com, Darren Hart , Torvald Riegel , "Carlos O'Donell" , Ingo Molnar , Jakub Jelinek , linux-man , lkml , Davidlohr Bueso , Arnd Bergmann , Steven Rostedt , Linux API , Roland McGrath , Anton Blanchard , Eric Dumazet , bill o gallmeister , Jan Kiszka , Daniel Wagner , Rich Felker , Andy Lutomirski , bert hubert , Rusty Russell , Heinrich Schuchardt Subject: Re: Next round: revised futex(2) man page for review References: <55B61EF3.7080302@gmail.com> <20150728204508.GG19282@twins.programming.kicks-ass.net> In-Reply-To: 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: 1756 Lines: 49 On 07/28/2015 11:03 PM, Thomas Gleixner wrote: > On Tue, 28 Jul 2015, Peter Zijlstra wrote: > >> On Tue, Jul 28, 2015 at 10:23:51PM +0200, Thomas Gleixner wrote: >> >>>> FUTEX_WAKE (since Linux 2.6.0) >>>> This operation wakes at most val of the waiters that are >>>> waiting (e.g., inside FUTEX_WAIT) on the futex word at the >>>> address uaddr. Most commonly, val is specified as either >>>> 1 (wake up a single waiter) or INT_MAX (wake up all wait‐ >>>> ers). 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). >>> >>> That's only correct up to Linux 2.6.21. >>> >>> Since 2.6.22 we have a priority ordered wakeup. For SCHED_OTHER >>> threads this takes the nice level into account. Threads with the same >>> priority are woken in FIFO order. >> >> Maybe don't mention the effects of SCHED_OTHER, order by nice value is >> 'wrong'. > > Indeed. > >> Also, this code seems to use plist, which means it won't do the right >> thing for SCHED_DEADLINE either. >> >> Do we want to go fix that? > > I think so. So, no change to this piece of text then? 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/