Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752273AbbLNQvc (ORCPT ); Mon, 14 Dec 2015 11:51:32 -0500 Received: from casper.infradead.org ([85.118.1.10]:45891 "EHLO casper.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750924AbbLNQvb (ORCPT ); Mon, 14 Dec 2015 11:51:31 -0500 Date: Mon, 14 Dec 2015 17:51:28 +0100 From: Peter Zijlstra To: Vincent Guittot Cc: Steve Muckle , Ingo Molnar , linux-kernel , "linux-pm@vger.kernel.org" , Morten Rasmussen , Dietmar Eggemann , Juri Lelli , Patrick Bellasi , Michael Turquette , Luca Abeni Subject: Re: [RFCv6 PATCH 09/10] sched: deadline: use deadline bandwidth in scale_rt_capacity Message-ID: <20151214165128.GU6357@twins.programming.kicks-ass.net> References: <1449641971-20827-1-git-send-email-smuckle@linaro.org> <1449641971-20827-10-git-send-email-smuckle@linaro.org> <20151214151729.GQ6357@twins.programming.kicks-ass.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2012-12-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1528 Lines: 30 On Mon, Dec 14, 2015 at 04:56:17PM +0100, Vincent Guittot wrote: > I agree that if the WCET is far from reality, we will underestimate > available capacity for CFS. Have you got some use case in mind which > overestimates the WCET ? Pretty much any 'correct' WCET is pessimistic. There's heaps of smart people working on improving WCET bounds, but they're still out there. This is mostly because of the .00001% tail cases that 'never' happen but would make your tokamak burn a hole just when you're outside. > If we can't rely on this parameters to evaluate the amount of capacity > used by deadline scheduler on a core, this will imply that we can't > also use it for requesting capacity to cpufreq and we should fallback > on a monitoring mechanism which reacts to a change instead of > anticipating it. No, since the WCET can and _will_ happen, its the best you can do with cpufreq. If you were to set it lower you could not be able to execute correctly in your 'never' tail cases. There 'might' be smart pants ways around this, where you run part of the execution at lower speed and switch to a higher speed to 'catch' up if you exceed some boundary, such that, on average, you run at the same speed the WCET mandates, but I'm not sure that's worth it. Juri/Luca might know. -- 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/