From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S967384AbcA1LPK (ORCPT ); Thu, 28 Jan 2016 06:15:10 -0500 Received: from mail-wm0-f50.google.com ([74.125.82.50]:35249 "EHLO mail-wm0-f50.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S966712AbcA1LOt (ORCPT ); Thu, 28 Jan 2016 06:14:49 -0500 Date: Thu, 28 Jan 2016 12:14:41 +0100 From: luca abeni To: Peter Zijlstra Cc: linux-kernel@vger.kernel.org, Ingo Molnar , Juri Lelli Subject: Re: [RFC 4/8] Improve the tracking of active utilisation Message-ID: <20160128121441.0ebde65d@utopia> In-Reply-To: <20160127143946.GR6357@twins.programming.kicks-ass.net> References: <1452785094-3086-1-git-send-email-luca.abeni@unitn.it> <1452785094-3086-5-git-send-email-luca.abeni@unitn.it> <20160114194323.GC6357@twins.programming.kicks-ass.net> <569E29FD.9040909@unitn.it> <20160119134739.GY6357@twins.programming.kicks-ass.net> <20160127143651.4de18ad9@luca-1225C> <20160127143946.GR6357@twins.programming.kicks-ass.net> Organization: university of trento X-Mailer: Claws Mail 3.12.0 (GTK+ 2.24.28; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Peter, On Wed, 27 Jan 2016 15:39:46 +0100 Peter Zijlstra wrote: > On Wed, Jan 27, 2016 at 02:36:51PM +0100, Luca Abeni wrote: > > Ok, so I implemented this idea, and I am currently testing it... > > The first experiments seem to show that there are no problems, but I > > just tried some simple workload (rt-app, or some other periodic > > taskset scheduled by SCHED_DEADLINE). Do you have suggestions for > > more "interesting" (and meaningful) tests/experiments? > > rt-app is the workload generator, right? > > I think the most interesting part here is the switched_from path, so > you'd want the workload to include a !rt task that gets PI boosted to > deadline every so often. I am looking at the PI stuff right now... And I am not sure if SCHED_DEADLINE does the right thing for PI :) Anyway, I think the total SCHED_DEADLINE utilization (rd->dl_bw) is currently not changed when a SCHED_OTHER task is boosted to SCHED_DEADLINE due to PI... Right? Is this the desired behaviour? If yes, I'll make sure that my patch does not change it. Thanks, Luca