Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S964785AbWCNWCn (ORCPT ); Tue, 14 Mar 2006 17:02:43 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S964789AbWCNWCn (ORCPT ); Tue, 14 Mar 2006 17:02:43 -0500 Received: from lirs02.phys.au.dk ([130.225.28.43]:32909 "EHLO lirs02.phys.au.dk") by vger.kernel.org with ESMTP id S964785AbWCNWCl (ORCPT ); Tue, 14 Mar 2006 17:02:41 -0500 Date: Tue, 14 Mar 2006 23:02:31 +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: <20060314101811.GA10450@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: 655 Lines: 20 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. Esben - 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/