Received: by 10.223.185.116 with SMTP id b49csp6180963wrg; Thu, 8 Mar 2018 03:15:07 -0800 (PST) X-Google-Smtp-Source: AG47ELsibQPEBcKWFWCP57hvlSqF3wqrVaE1++yvr9WbcaL+Jqer4LhDJdfFN6eTqH6nPkZTUunk X-Received: by 10.98.49.135 with SMTP id x129mr25836412pfx.75.1520507707033; Thu, 08 Mar 2018 03:15:07 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1520507707; cv=none; d=google.com; s=arc-20160816; b=PSKpCJQzj13wAaQwud58+2YPZVsnboyy//zLdaKBLNCr2aZhv8GuT/5c3pwUnWILxQ N+sDgwp7Xx3jc1OSNpPvFnfBFFh4LX6lnraYbgxr4m65Dzm7QqTC3yNDbNX7MD2jgOGL lRwm/5yP1SkjV+pzib3SJtchOJPQnyTied/4v3QzKwRKW4xNg9AotLnsi7DX+ER3sMoC SNb/3W9aaOtrVPSGz0A3oZH3rVFyXPZ0Ar8A+DyS8Sd9Y5/QWKpdtPZmR4bTBinTHQCN p1XrwBeZtO+gZgoWafryupiU95BBrxDhu/i2wwNTRrbIdrnQ2nWTbGIK3RyHMkjdgZWi IJ2g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :references:in-reply-to:mime-version:dkim-signature :arc-authentication-results; bh=qIChHthYrYqhDb16iM00GMatzfoZ89TQvfwmmnnGG+M=; b=KuB5dcd5Vvzes2sqcNeBOkR06cRMEqDYL7ho5hXa/IevNSkdnrFaOSLtpSlJyeITPZ SEnq5DQuLkWblhN4lfUAranswgEoilSpXGaoj4o7VblYpIMePlYguO2C+bZiOeRS/+dB pa823m1PkMeY1usN7Gv5KmcN4P5fmQ0ke1s5II4Kc4ulu64l8+INDxrvOkL5qLGuupRh jTQZpONAAuV/jIqTa6n7aLT+Fd8WtB0Af9hmiiVwEdi7sCHPJaWVwoR0Cs5mZAFsdvqv v+YPn76xX6EDDbFn4sYO2TXOcaCx5JmGJ5EDFTvpkeqH57ZhDGRvOEdMXlc2SoJpZEAv h3kg== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@gmail.com header.s=20161025 header.b=D4PtOGZc; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id u16si15610206pfl.299.2018.03.08.03.14.51; Thu, 08 Mar 2018 03:15:06 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=fail header.i=@gmail.com header.s=20161025 header.b=D4PtOGZc; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S935784AbeCHLNE (ORCPT + 99 others); Thu, 8 Mar 2018 06:13:04 -0500 Received: from mail-ot0-f196.google.com ([74.125.82.196]:37689 "EHLO mail-ot0-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S935768AbeCHLNC (ORCPT ); Thu, 8 Mar 2018 06:13:02 -0500 Received: by mail-ot0-f196.google.com with SMTP id t2so5046043otj.4; Thu, 08 Mar 2018 03:13:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=qIChHthYrYqhDb16iM00GMatzfoZ89TQvfwmmnnGG+M=; b=D4PtOGZc2XwJqJtLV45OPvIXqf0idGqq7qpDxx58VI9tDeFNaVDPIyzXaUndRKW3di WZiSxJjLMppQWHw7TizPcKbXVXDdXMMltUNCyvO9rRM+LujoRdO3raUdGiJx/Pir38Qu dVwCqKVvV65PgXTFBiJHig3MigYShhS4/+wJ4XpHGNhV59S5LeMGsJy4MydNntL46YIr vijRZ4rvbFlLYkBKLXP8hZrMF4CQV1/uBiegxcCQ7AfB81mrnYhfuwwhUdD9CoMfEiUW iGRPst10yxm4di0Jqfvgbaq+sFVkgFLQUM1lRV43KhyqVubPFyXGtEwydpSfgr06y1Ly Kzcw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=qIChHthYrYqhDb16iM00GMatzfoZ89TQvfwmmnnGG+M=; b=d6yptolwAygqKeIFxOu6kOjT5bgYUbagGLlCLq3Bcj3Naga8xz409Cgfcf6rfHMrtb lzZps0CIL08WRTMIhDxrPEp60rHIXnZfmbQoJlaueSOIk8v2W/FWQlAIpAUuSEKBctc1 90Zr9aEWOX8/uENBbP9aFQhWuHg1WX+6smyySYL1rfgJJ9dg90tNChV0VPTPbLfRWmnU Wp3PCabLfUhMYh/b7MUdV85B1by0zp4TBjyUOnq8KCrRNLwbUtwITgrE8l2k9DUu4oZ9 v0LlNdxRZceRaWt+VkBmMQLwWpFXJ15Jj4CYMfC8vPxaM6F/NKGFU031k/exmGlr3qFW 1yaQ== X-Gm-Message-State: AElRT7E/GFnIjLmyS3ZvdHjrrBvaT1srr14Tof5bQk/Kt5fwcADihWeF GR1PB6XrbIYysaP5nXijNzQEnDf3rwBK6f9ci60= X-Received: by 10.157.38.175 with SMTP id l44mr18463214otb.217.1520507582147; Thu, 08 Mar 2018 03:13:02 -0800 (PST) MIME-Version: 1.0 Received: by 10.157.44.146 with HTTP; Thu, 8 Mar 2018 03:13:01 -0800 (PST) In-Reply-To: <1520504950-8544-1-git-send-email-claudio@evidence.eu.com> References: <1520504950-8544-1-git-send-email-claudio@evidence.eu.com> From: "Rafael J. Wysocki" Date: Thu, 8 Mar 2018 12:13:01 +0100 X-Google-Sender-Auth: atjY2o9LNanFvqaZrBxqOoQp6RU Message-ID: Subject: Re: [PATCH v3] cpufreq: schedutil: rate limits for SCHED_DEADLINE To: Claudio Scordino Cc: Peter Zijlstra , "Rafael J . Wysocki" , Ingo Molnar , Patrick Bellasi , Dietmar Eggemann , Morten Rasmussen , Juri Lelli , Viresh Kumar , Vincent Guittot , Todd Kjos , Joel Fernandes , Linux PM , Linux Kernel Mailing List Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Mar 8, 2018 at 11:29 AM, Claudio Scordino wrote: > When the SCHED_DEADLINE scheduling class increases the CPU utilization, > we should not wait for the rate limit, otherwise we may miss some > deadline. > > Tests using rt-app on Exynos5422 with up to 10 SCHED_DEADLINE tasks have > shown reductions of even 10% of deadline misses with a negligible > increase of energy consumption (measured through Baylibre Cape). > > Signed-off-by: Claudio Scordino > CC: Ingo Molnar > CC: Patrick Bellasi > CC: Dietmar Eggemann > CC: Morten Rasmussen > CC: Juri Lelli > CC: Viresh Kumar > CC: Vincent Guittot > CC: Todd Kjos > CC: Joel Fernandes > CC: linux-pm@vger.kernel.org > CC: linux-kernel@vger.kernel.org > --- > Changes from v2: > - Rate limit ignored also in case of "fast switch" > - Specific routine added > --- > Changes from v1: > - Logic moved from sugov_should_update_freq() to > sugov_update_single()/_shared() to not duplicate data structures > - Rate limit not ignored in case of "fast switch" > --- > kernel/sched/cpufreq_schedutil.c | 15 +++++++++++++++ > 1 file changed, 15 insertions(+) > > diff --git a/kernel/sched/cpufreq_schedutil.c b/kernel/sched/cpufreq_schedutil.c > index 7936f54..13f9cce 100644 > --- a/kernel/sched/cpufreq_schedutil.c > +++ b/kernel/sched/cpufreq_schedutil.c > @@ -260,6 +260,17 @@ static bool sugov_cpu_is_busy(struct sugov_cpu *sg_cpu) > static inline bool sugov_cpu_is_busy(struct sugov_cpu *sg_cpu) { return false; } > #endif /* CONFIG_NO_HZ_COMMON */ > > +/* > + * Make sugov_should_update_freq() ignore the rate limit when DL > + * has increased the utilization. > + */ > +static inline I wouldn't break the line here > +void set_dl_rate_limit(struct sugov_cpu *sg_cpu, struct sugov_policy *sg_policy) and the name might be better as Viresh said, but overall Reviewed-by: Rafael J. Wysocki > +{ > + if (cpu_util_dl(cpu_rq(sg_cpu->cpu)) > sg_cpu->util_dl) > + sg_policy->need_freq_update = true; > +} > + > static void sugov_update_single(struct update_util_data *hook, u64 time, > unsigned int flags) > { > @@ -273,6 +284,8 @@ static void sugov_update_single(struct update_util_data *hook, u64 time, > sugov_set_iowait_boost(sg_cpu, time); > sg_cpu->last_update = time; > > + set_dl_rate_limit(sg_cpu, sg_policy); > + > if (!sugov_should_update_freq(sg_policy, time)) > return; > > @@ -354,6 +367,8 @@ static void sugov_update_shared(struct update_util_data *hook, u64 time, > > raw_spin_lock(&sg_policy->update_lock); > > + set_dl_rate_limit(sg_cpu, sg_policy); > + > sugov_get_util(sg_cpu); > sg_cpu->flags = flags; > > -- > 2.7.4 >