From: Shilpasri G Bhat <shilpa.bhat@linux.vnet.ibm.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Viresh Kumar <viresh.kumar@linaro.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"Gautham R. Shenoy" <ego@linux.vnet.ibm.com>,
shreyas@linux.vnet.ibm.com, akshay.adiga@linux.vnet.ibm.com,
linuxppc-dev@ozlabs.org, Steve Muckle <steve.muckle@linaro.org>
Subject: Re: [RFC PATCH] Increase in idle power with schedutil
Date: Fri, 20 May 2016 17:53:41 +0530 [thread overview]
Message-ID: <573F01CD.6030107@linux.vnet.ibm.com> (raw)
In-Reply-To: <20160519114029.GW3193@twins.programming.kicks-ass.net>
Hi,
On 05/19/2016 05:10 PM, Peter Zijlstra wrote:
> On Wed, May 18, 2016 at 11:11:51PM +0200, Rafael J. Wysocki wrote:
>> On Wed, May 18, 2016 at 2:53 PM, Shilpasri G Bhat
>> <shilpa.bhat@linux.vnet.ibm.com> wrote:
>>> This patch adds driver callback for fast_switch and below observations
>>> on schedutil governor are done with this patch.
>>>
>>> In POWER8 there is a regression observed with schedutil compared to
>>> ondemand. With schedutil the frequency is not ramping down and is
>>> mostly stuck at max frequency during idle . This is because of the
>>> watchdog timer, an RT task which is fired every 4 seconds which
>>> results in requesting max frequency.
>>
>> Well, yes, that would be problematic.
>>
>
> Right; we need to come up with something for RT tasks; but what happens
> if you disable the watchdog? This should be entirely doable and might
> give a better comparison.
>
Below are the comparisons by disabling watchdog.
Both schedutil and ondemand have a similar ramp-down trend. And in both the
cases I can see that frequency of the cpu is not reduced in deterministic
fashion. In a observation window of 30 seconds after running a workload I can
see that the frequency is not ramped down on some cpus in the system and are
idling at max frequency.
Below are the sample trace showcasing the frequency request when the cpu enters
idle with schedutil.
<...>-3528 7650.011010: cpu_frequency: state=4322000 cpu_id=120
<...>-3528 7650.027540: sched_switch: prev_comm=ppc64_cpu prev_state=x ==>
next_comm=swapper/120
<idle>-0 7650.035017: cpu_frequency: state=4322000 cpu_id=120
<idle>-0 7729.683536: cpu_frequency: state=4322000 cpu_id=120
<idle>-0 7729.683552: sched_switch: prev_comm=swapper/120 prev_state=R ==>
next_comm=kworker/120:1
kworker/120 7729.683565: sched_switch: prev_comm=kworker/120:1 prev_state=S ==>
next_comm=swapper/120
However ondemand governor(with watchdog enabled) benefits from the noise created
by watchdog timer and is able to brig down the frequency.
Thanks and Regards,
Shilpa
next prev parent reply other threads:[~2016-05-20 12:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-18 12:53 [RFC PATCH] Increase in idle power with schedutil Shilpasri G Bhat
2016-05-18 12:53 ` [RFC PATCH] cpufreq: powernv: Add fast_switch callback Shilpasri G Bhat
2016-05-18 21:22 ` Rafael J. Wysocki
2016-05-18 21:11 ` [RFC PATCH] Increase in idle power with schedutil Rafael J. Wysocki
2016-05-19 11:40 ` Peter Zijlstra
2016-05-19 14:30 ` Rafael J. Wysocki
2016-05-20 12:23 ` Shilpasri G Bhat [this message]
[not found] ` <201605201223.u4KCNWn9028105@mx0a-001b2d01.pphosted.com>
2016-05-22 10:39 ` Peter Zijlstra
2016-05-22 20:42 ` Steve Muckle
2016-05-23 9:00 ` Lorenzo Pieralisi
2016-05-23 9:24 ` Peter Zijlstra
2016-05-23 9:24 ` Peter Zijlstra
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=573F01CD.6030107@linux.vnet.ibm.com \
--to=shilpa.bhat@linux.vnet.ibm.com \
--cc=akshay.adiga@linux.vnet.ibm.com \
--cc=ego@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=peterz@infradead.org \
--cc=rjw@rjwysocki.net \
--cc=shreyas@linux.vnet.ibm.com \
--cc=steve.muckle@linaro.org \
--cc=viresh.kumar@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).