From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261285AbULMWg3 (ORCPT ); Mon, 13 Dec 2004 17:36:29 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261241AbULMWfD (ORCPT ); Mon, 13 Dec 2004 17:35:03 -0500 Received: from mx2.elte.hu ([157.181.151.9]:22491 "EHLO mx2.elte.hu") by vger.kernel.org with ESMTP id S261346AbULMWcF (ORCPT ); Mon, 13 Dec 2004 17:32:05 -0500 Date: Mon, 13 Dec 2004 23:31:53 +0100 From: Ingo Molnar To: Steven Rostedt Cc: Mark Johnson , Amit Shah , Karsten Wiese , Bill Huey , Adam Heath , emann@mrv.com, Gunther Persoons , "K.R. Foley" , LKML , Florian Schmidt , Fernando Pablo Lopez-Lezcano , Lee Revell , Rui Nuno Capela , Shane Shrybman , Esben Nielsen , Thomas Gleixner , Michal Schmidt Subject: Re: [patch] Real-Time Preemption, -RT-2.6.10-rc2-mm3-V0.7.32-6 Message-ID: <20041213223153.GA6793@elte.hu> References: <1102722147.3300.7.camel@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1102722147.3300.7.camel@localhost.localdomain> User-Agent: Mutt/1.4.1i X-ELTE-SpamVersion: MailScanner 4.31.6-itk1 (ELTE 1.2) SpamAssassin 2.63 ClamAV 0.73 X-ELTE-VirusStatus: clean X-ELTE-SpamCheck: no X-ELTE-SpamCheck-Details: score=-4.9, required 5.9, autolearn=not spam, BAYES_00 -4.90 X-ELTE-SpamLevel: X-ELTE-SpamScore: -4 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org * Steven Rostedt wrote: > [RFC] Has there been previously any thought of adding priority > inheriting wait queues. [...] this will make sense at a certain point. > [...] it would really help to solve the problem of a high priority > process waiting for an interrupt that can be starved by other high > priority processes. the primary use i think would be kernel-internal task <-> task waitqueues such as the futex queues, to transport the effects of RT priorities across waitqueues as well. IRQ related waitqueues are a nice 'side-effect'. another next step would be to transport PI effects to userspace code, for user-controlled synchronization objects such as futexes or e.g. SysV semaphores. Ingo