Received: by 2002:ac0:a594:0:0:0:0:0 with SMTP id m20-v6csp4647828imm; Mon, 14 May 2018 10:30:34 -0700 (PDT) X-Google-Smtp-Source: AB8JxZpAQRd5RzXVXbvorU+SzyCCi0rNxsHyTQDpUN4csx6AP2gzRJgcsWPJAMdTZjTi8oX9qJRK X-Received: by 2002:a65:64c7:: with SMTP id t7-v6mr9440817pgv.274.1526319034566; Mon, 14 May 2018 10:30:34 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1526319034; cv=none; d=google.com; s=arc-20160816; b=HOUUJkwuug/p5He/joQnoxe0gBK+WtVdC64vfx7gsYTyb5bcjMB/5dIXf3dfygPCq4 FeYHM+htTl8mbeOkw7vT5YQcweaYRzPIJYdALUbY9CK0y++grSxgXK4FBEnBG/FoV6s8 701qHMxi8FafJQZwxsuuKCQGirDKttodRL7/oAGZFrRErlD2ItFHrZBpQPHqb8tTLofl BIWi/NueFBBf8/TXnr1Gu5FbssCumiJ3qSUQMd5fXL+OLixh+i1LHhovPRzUK01KZ6uk Xd02B4LKvcyWZ1yfD79M12NRL40mBJth7YpMdwZKEBVnNSvoSKnq+SGpm0eoiJQ3Ivcq J6cg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:arc-authentication-results; bh=zgtOInhphc5iO3/Mpeg9ABjgfGkgEE5C6vLyRo8tHBE=; b=puKSo0CzwqKq7FPAFwdOt4vuUi5RV3wpjEKErDruCDANMAUHOU3/KfpCNhfPvEm3Il mAzoKh3ixeI39b5tiujHI0ktY+S9FMQGD4r4Np7d4mrenEDR76NwLY1x51OI0nUxucIs zrWQ4MN2XM7XJbzqNxThQWROpLpmXSUMWyQf4jfwuUQdvmrb6P+vF8FwP/nSylllfMfB xiNnV5VUIc6RoKEOE06FFC/DCeoPdlDJgNJkfC2xI8baCkoZOlJIVKv5JDAVtlVyjaIt vPV+E3ozGiDHx5yaManxh3tjH069qpCkOyuPnd4/PmI4E8xNDxh0tlukPScIeVm/Nn6C QusQ== 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 v12-v6si4927264pgs.538.2018.05.14.10.30.19; Mon, 14 May 2018 10:30:34 -0700 (PDT) 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 S1755059AbeENQsS (ORCPT + 99 others); Mon, 14 May 2018 12:48:18 -0400 Received: from foss.arm.com ([217.140.101.70]:46490 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754777AbeENQsR (ORCPT ); Mon, 14 May 2018 12:48:17 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.72.51.249]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id CE23E1596; Mon, 14 May 2018 09:48:16 -0700 (PDT) Received: from e110439-lin (e110439-lin.cambridge.arm.com [10.1.210.68]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id BC8FB3F59F; Mon, 14 May 2018 09:48:14 -0700 (PDT) Date: Mon, 14 May 2018 17:48:12 +0100 From: Patrick Bellasi To: Vincent Guittot Cc: linux-kernel , "open list:THERMAL" , Ingo Molnar , Peter Zijlstra , "Rafael J . Wysocki" , Viresh Kumar , Dietmar Eggemann , Morten Rasmussen , Juri Lelli , Joel Fernandes , Steve Muckle Subject: Re: [PATCH v2 1/3] sched/cpufreq: always consider blocked FAIR utilization Message-ID: <20180514164812.GI30654@e110439-lin> References: <20180511131509.16275-1-patrick.bellasi@arm.com> <20180511131509.16275-2-patrick.bellasi@arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 14-May 11:16, Vincent Guittot wrote: > Hi Patrick, Hi Vincent, > On 11 May 2018 at 15:15, Patrick Bellasi wrote: > > Since the refactoring introduced by: > > > > commit 8f111bc357aa ("cpufreq/schedutil: Rewrite CPUFREQ_RT support") > > > > we aggregate FAIR utilization only if this class has runnable tasks. > > This was mainly due to avoid the risk to stay on an high frequency just > > because of the blocked utilization of a CPU not being properly decayed > > while the CPU was idle. > > > > However, since: > > > > commit 31e77c93e432 ("sched/fair: Update blocked load when newly idle") > > > > the FAIR blocked utilization is properly decayed also for IDLE CPUs. > > > > This allows us to use the FAIR blocked utilization as a safe mechanism > > to gracefully reduce the frequency only if no FAIR tasks show up on a > > CPU for a reasonable period of time. > > > > Moreover, we also reduce the frequency drops of CPUs running periodic > > tasks which, depending on the task periodicity and the time required > > for a frequency switch, was increasing the chances to introduce some > > undesirable performance variations. > > > > Reported-by: Vincent Guittot > > Signed-off-by: Patrick Bellasi > > Acked-by: Viresh Kumar > > Cc: Ingo Molnar > > Cc: Peter Zijlstra > > Cc: Rafael J. Wysocki > > Cc: Vincent Guittot > > Cc: Viresh Kumar > > Cc: Joel Fernandes > > Cc: linux-kernel@vger.kernel.org > > Cc: linux-pm@vger.kernel.org > > With this patch, I can't see the spurious OPP changes that I was seeing before Cool thanks... regarding OPP updates I've added some more comments in my reply to Joel's comments to my last patch of this series. Would be nice if you can have a look... toward the end there are some considerations about schedutil updates (indirectly) triggered by your patches for blocked load updates on IDLE CPUs. > FWIW > Acked-by: Vincent Guittot > Tested-by: Vincent Guittot Thanks for testing, will add these to the next respin. -- #include Patrick Bellasi