Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S270770AbUJURnO (ORCPT ); Thu, 21 Oct 2004 13:43:14 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S270789AbUJURnG (ORCPT ); Thu, 21 Oct 2004 13:43:06 -0400 Received: from host-65-117-135-105.timesys.com ([65.117.135.105]:24212 "EHLO yoda.timesys") by vger.kernel.org with ESMTP id S270770AbUJURlt (ORCPT ); Thu, 21 Oct 2004 13:41:49 -0400 Date: Thu, 21 Oct 2004 13:41:09 -0400 To: "Eugeny S. Mints" Cc: john cooper , Esben Nielsen , Ingo Molnar , Thomas Gleixner , Jens Axboe , Rui Nuno Capela , LKML , Lee Revell , mark_h_johnson@raytheon.com, "K.R. Foley" , Bill Huey , Adam Heath , Florian Schmidt , Michal Schmidt , Fernando Pablo Lopez-Lezcano Subject: Re: [patch] Real-Time Preemption, -RT-2.6.9-rc4-mm1-U8 Message-ID: <20041021174109.GB26318@yoda.timesys> References: <4177CD3C.9020201@timesys.com> <4177DA11.4090902@ru.mvista.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4177DA11.4090902@ru.mvista.com> User-Agent: Mutt/1.5.4i From: Scott Wood Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 878 Lines: 18 On Thu, Oct 21, 2004 at 07:47:29PM +0400, Eugeny S. Mints wrote: > Seems it is too coplex model at least for the first step. The one of > possible trade-offs coming on mind is to trace the number of resources > (mutexes) held by a process and to restore original priority only when > resource count reaches 0. This is one of the sollutions accepted by RTOS > guys. That complicates analysis, though, since you now have to look at all critical sections that the shared-with-high-priority-threads critical sections nest in. IMHO, it's important that the inherited priority be given up as soon as the resource is released. -Scott - 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/