Received: by 10.223.176.5 with SMTP id f5csp506110wra; Fri, 9 Feb 2018 02:39:10 -0800 (PST) X-Google-Smtp-Source: AH8x226EUG0mJCbfwqhRiZhKShDIg8g1bgsgGz2/Eq8iAypVFCduSutvFUoQgKOaBisx6RR7iKBs X-Received: by 10.98.33.199 with SMTP id o68mr2401171pfj.78.1518172750535; Fri, 09 Feb 2018 02:39:10 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1518172750; cv=none; d=google.com; s=arc-20160816; b=w/RuumkWpjd77LPG41mcZNMrkeIbPXbaMJIcgB8cp2teL9iq8spRNRQ7PcjLboCC3k X0gSypPjkvcXAQonyeoWHwZvrxk7DWi1LLChUbuI/SxaZqDl5UvtqSiKuqfyMJmV8d0p 4x0r2UYuxlnNS4erfU7ICgp5vBGRacRQZsGE3pIxb9DVNohidNTIgORf7GxMz7KcUD/X zP9LVo1R7e12k0AfTXcYaU5R1b5NcmPoLcMKlZZbdWGRt9ROP6iMB/8IzNSQPILCuXeM x73rViU5cRWxg32eG+HAZq0ADWs207IJ2xrUK+gQR1TXLFSoZ+QhM4M/yKE5vMn76uvW djNw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from :arc-authentication-results; bh=DjBNv5ChFbssK+2ssgyBDPIIKD1MO3pppGiGz1lhOt0=; b=CythbHRKUMqkbdZwqEeHydTonkvwy0beKo1n20GvyKLVOBOsDM1FEZWnfz8NABauWX i/icTHAfuaKq/LqMS8Tr9LWEPAkyzVxaTdUk/WvLBnQpYInPQQdCYInI/6/iGa/kYd9g Uo4p91KzvHjIlMgvKBnxo6ju4jgkfdnxeX1JkEvF4Iow4If6r6GoDhCGKJly0Msz08xU scaeFIuBmED+UsxffHmf7QZHJ+y+kaoB2ATZLIiVF1JjLVllAWj90nRdJTXGjgQQGjZM PcL6zU/YRdY5di9t3y3cssf5SX9yvx8DNmAQr/7i9R6BfSAk0hej6OpwJMkSTQV+8aDQ HoDA== ARC-Authentication-Results: i=1; mx.google.com; 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 w9-v6si1361976plp.58.2018.02.09.02.38.55; Fri, 09 Feb 2018 02:39:10 -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; 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 S1751048AbeBIKiQ (ORCPT + 99 others); Fri, 9 Feb 2018 05:38:16 -0500 Received: from cloudserver094114.home.pl ([79.96.170.134]:55401 "EHLO cloudserver094114.home.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750961AbeBIKiP (ORCPT ); Fri, 9 Feb 2018 05:38:15 -0500 Received: from 79.184.255.223.ipv4.supernova.orange.pl (79.184.255.223) (HELO aspire.rjw.lan) by serwer1319399.home.pl (79.96.170.134) with SMTP (IdeaSmtpServer 0.83) id 4c0b6c7d942df979; Fri, 9 Feb 2018 11:38:13 +0100 From: "Rafael J. Wysocki" To: Claudio Scordino Cc: Viresh Kumar , Peter Zijlstra , Ingo Molnar , "Rafael J . Wysocki" , Patrick Bellasi , Dietmar Eggemann , Morten Rasmussen , Juri Lelli , Vincent Guittot , Todd Kjos , Joel Fernandes , linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] cpufreq: schedutil: rate limits for SCHED_DEADLINE Date: Fri, 09 Feb 2018 11:36:30 +0100 Message-ID: <11598161.veS9VGWB8G@aspire.rjw.lan> In-Reply-To: <197c26ba-c2a6-2de7-dffa-5b884079f746@evidence.eu.com> References: <1518109302-8239-1-git-send-email-claudio@evidence.eu.com> <20180209035143.GX28462@vireshk-i7> <197c26ba-c2a6-2de7-dffa-5b884079f746@evidence.eu.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Friday, February 9, 2018 9:02:34 AM CET Claudio Scordino wrote: > Hi Viresh, > > Il 09/02/2018 04:51, Viresh Kumar ha scritto: > > On 08-02-18, 18:01, 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 have shown reductions of about 10% of deadline > >> misses for tasks with low RT periods. > >> > >> The patch applies on top of the one recently proposed by Peter to drop the > >> SCHED_CPUFREQ_* flags. > >> [cut] > > > > > Is it possible to (somehow) check here if the DL tasks will miss > > deadline if we continue to run at current frequency? And only ignore > > rate-limit if that is the case ? > > I need to think further about it. That would be my approach FWIW. Increasing the frequency beyond what is necessary means wasting energy in any case. Thanks, Rafael