Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751948AbWCNW2e (ORCPT ); Tue, 14 Mar 2006 17:28:34 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751947AbWCNW2e (ORCPT ); Tue, 14 Mar 2006 17:28:34 -0500 Received: from lirs02.phys.au.dk ([130.225.28.43]:3983 "EHLO lirs02.phys.au.dk") by vger.kernel.org with ESMTP id S1751944AbWCNW2e (ORCPT ); Tue, 14 Mar 2006 17:28:34 -0500 Date: Tue, 14 Mar 2006 23:28:28 +0100 (MET) From: Esben Nielsen To: Ingo Molnar cc: linux-kernel@vger.kernel.org, Thomas Gleixner Subject: Re: 2.6.16-rc6-rt1 In-Reply-To: <20060314221111.GA7118@elte.hu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1579 Lines: 46 On Tue, 14 Mar 2006, Ingo Molnar wrote: > > * Esben Nielsen wrote: > > > On Tue, 14 Mar 2006, Ingo Molnar wrote: > > > > > > > > * Esben Nielsen wrote: > > > > > > [...] > > > no. We have to run deadlock detection to avoid things like circular lock > > > dependencies causing an infinite schedule+wakeup 'storm' during priority > > > boosting. (like possible with your wakeup based method i think) > > No, all tasks would just settle on the highest priority and then the > > wakeups would stop. > > you are right, that shouldnt be possible. But how about other, SMP > artifacts? What if the woken up task runs on another CPU, and the whole > chain of boosting is thus delayed? > Yes, it will take longer that way. But it still ought to be _deterministic_. PI has never been a cheap. It is only safe guard against priority inversion. I am not saying using the scheduler is the best solution and certainly not the cheapest solution. It just popped up in my head and it seemed to work and was relatively easy to implement. Esben > Ingo > - > 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/ > - 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/