From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter Zijlstra Subject: Re: [RFC][PATCH v2 2/2] cpufreq: schedutil: Avoid decreasing frequency of busy CPUs Date: Tue, 21 Mar 2017 16:02:10 +0100 Message-ID: <20170321150210.GT3093@worktop> References: <4366682.tsferJN35u@aspire.rjw.lan> <20170321132253.vjp7f72qkubpttmf@hirez.programming.kicks-ass.net> <3429350.K2FUBgvcIK@aspire.rjw.lan> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <3429350.K2FUBgvcIK@aspire.rjw.lan> Sender: linux-kernel-owner@vger.kernel.org To: "Rafael J. Wysocki" Cc: Vincent Guittot , Linux PM , LKML , Srinivas Pandruvada , Viresh Kumar , Juri Lelli , Patrick Bellasi , Joel Fernandes , Morten Rasmussen , Ingo Molnar List-Id: linux-pm@vger.kernel.org On Tue, Mar 21, 2017 at 03:26:06PM +0100, Rafael J. Wysocki wrote: > + if ((flags & SCHED_CPUFREQ_RT_DL) || this_rq()->rd->overload) { > next_f = policy->cpuinfo.max_freq; So this I think is wrong; rd->overload is set if _any_ of the CPUs in the root domain is overloaded. And given the root domain is typically the _entire_ machine, this would have a tendency to run at max_freq far too often.