Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932555AbXAJMEH (ORCPT ); Wed, 10 Jan 2007 07:04:07 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932556AbXAJMEH (ORCPT ); Wed, 10 Jan 2007 07:04:07 -0500 Received: from ecfrec.frec.bull.fr ([129.183.4.8]:48476 "EHLO ecfrec.frec.bull.fr" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932555AbXAJMEF (ORCPT ); Wed, 10 Jan 2007 07:04:05 -0500 Message-ID: <45A4D5FC.7060808@bull.net> Date: Wed, 10 Jan 2007 13:03:08 +0100 From: Pierre Peiffer User-Agent: Thunderbird 1.5.0.9 (X11/20061219) MIME-Version: 1.0 Cc: Ulrich Drepper , LKML , Dinakar Guniguntala , Jean-Pierre Dion , Ingo Molnar , Jakub Jelinek , Darren Hart , =?UTF-8?B?U8OpYmFzdGllbiBEdWd1w6k=?= Subject: Re: [PATCH 2.6.20-rc4 1/4] futex priority based wakeup References: <45A3B330.9000104@bull.net> <45A3BFC8.1030104@bull.net> <45A3C2CE.7070500@redhat.com> <45A4D249.8080904@bull.net> In-Reply-To: <45A4D249.8080904@bull.net> X-MIMETrack: Itemize by SMTP Server on ECN002/FR/BULL(Release 5.0.12 |February 13, 2003) at 10/01/2007 13:12:11, Serialize by Router on ECN002/FR/BULL(Release 5.0.12 |February 13, 2003) at 10/01/2007 13:12:12, Serialize complete at 10/01/2007 13:12:12 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=UTF-8; format=flowed To: unlisted-recipients:; (no To-header on input) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1029 Lines: 29 Pierre Peiffer a écrit : > Ulrich Drepper a écrit : >> >> I have never seen performance numbers for this. If it is punishing >> existing code in a measurable way I think it's not anacceptable default >> behavior. > May be, supposing it makes sense to respect the priority order only for > real-time pthreads, I can register all SCHED_OTHER threads to the same > MAX_RT_PRIO priotity ? Moreover, the performance must be considered, sure, but after all, "man pthread_cond_broadcast" says: << If more than one thread is blocked on a condition variable, the scheduling policy shall determine the order in which threads are unblocked. >> ... this is not true today ... (of course, "shall" does not mean "mandatory", I know ;-) ) -- Pierre - 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/