Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755049AbcDATXM (ORCPT ); Fri, 1 Apr 2016 15:23:12 -0400 Received: from mail-pf0-f181.google.com ([209.85.192.181]:34890 "EHLO mail-pf0-f181.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752767AbcDATXK (ORCPT ); Fri, 1 Apr 2016 15:23:10 -0400 Subject: Re: [Update][PATCH v7 7/7] cpufreq: schedutil: New governor based on scheduler utilization data To: "Rafael J. Wysocki" References: <7262976.zPkLj56ATU@vostro.rjw.lan> <6666532.7ULg06hQ7e@vostro.rjw.lan> <145931680.Kk1xSBT0Ro@vostro.rjw.lan> <56FEB4BA.4080403@linaro.org> Cc: "Rafael J. Wysocki" , Linux PM list , Juri Lelli , ACPI Devel Maling List , Linux Kernel Mailing List , Peter Zijlstra , Srinivas Pandruvada , Viresh Kumar , Vincent Guittot , Michael Turquette , Ingo Molnar From: Steve Muckle Message-ID: <56FECA9B.20902@linaro.org> Date: Fri, 1 Apr 2016 12:23:07 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1315 Lines: 34 On 04/01/2016 12:14 PM, Rafael J. Wysocki wrote: > On Fri, Apr 1, 2016 at 7:49 PM, Steve Muckle wrote: >> On 03/29/2016 07:00 PM, Rafael J. Wysocki wrote: >> ... >>> +config CPU_FREQ_GOV_SCHEDUTIL >>> + tristate "'schedutil' cpufreq policy governor" >>> + depends on CPU_FREQ >>> + select CPU_FREQ_GOV_ATTR_SET >>> + select IRQ_WORK >>> + help >>> + This governor makes decisions based on the utilization data provided >>> + by the scheduler. It sets the CPU frequency to be proportional to >>> + the utilization/capacity ratio coming from the scheduler. If the >>> + utilization is frequency-invariant, the new frequency is also >>> + proportional to the maximum available frequency. If that is not the >>> + case, it is proportional to the current frequency of the CPU with the >>> + tipping point at utilization/capacity equal to 80%. >> >> This help text implies that the tipping point of 80% applies only to >> non-frequency invariant configurations, rather than both. Possible to >> rephrase? > > Sure. > > What about: > > "If that is not the case, it is proportional to the current frequency > of the CPU. The frequency tipping point is at utilization/capacity > equal to 80% in both cases." LGTM thanks, Steve