From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756922Ab0KKWPm (ORCPT ); Thu, 11 Nov 2010 17:15:42 -0500 Received: from canuck.infradead.org ([134.117.69.58]:60889 "EHLO canuck.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754294Ab0KKWPl convert rfc822-to-8bit (ORCPT ); Thu, 11 Nov 2010 17:15:41 -0500 Subject: Re: [RFC][PATCH 20/22] sched: drafted deadline inheritance logic From: Peter Zijlstra To: Raistlin Cc: Ingo Molnar , Thomas Gleixner , Steven Rostedt , Chris Friesen , oleg@redhat.com, Frederic Weisbecker , Darren Hart , Johan Eker , "p.faure" , linux-kernel , Claudio Scordino , michael trimarchi , Fabio Checconi , Tommaso Cucinotta , Juri Lelli , Nicola Manica , Luca Abeni , Dhaval Giani , Harald Gustafsson , paulmck In-Reply-To: <1288334618.8661.162.camel@Palantir> References: <1288333128.8661.137.camel@Palantir> <1288334618.8661.162.camel@Palantir> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8BIT Date: Thu, 11 Nov 2010 23:15:15 +0100 Message-ID: <1289513715.2084.201.camel@laptop> Mime-Version: 1.0 X-Mailer: Evolution 2.30.3 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 2010-10-29 at 08:43 +0200, Raistlin wrote: > Some method to deal with rt-mutexes and make sched_dl interact with > the current PI-coded is needed, raising all but trivial issues, that > needs (according to us) to be solved with some restructuring of > the pi-code (i.e., going toward a proxy execution-ish implementation). > > This is under development, in the meanwhile, as a temporary solution, > what this commits does is: > - ensure a pi-lock owner with waiters is never throttled down. Instead, > when it runs out of runtime, it immediately gets replenished and it's > deadline is postponed (as in SF_BWRECL_DL reclaiming policy); > - the scheduling parameters (relative deadline and default runtime) > used for that replenishments --during the whole period it holds the > pi-lock-- are the ones of the waiting task with earliest deadline. > > Acting this way, we provide some kind of boosting to the lock-owner, > still by using the existing (actually, slightly modified by the previous > commit) pi-architecture. Right, so this is the trivial priority ceiling protocol extended to bandwidth inheritance and we basically let the owner overrun its runtime to release the shared resource. Didn't look at it too closely, but yeah, that is a sensible first approximation band-aid to keep stuff working.