From: "Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: viresh.kumar@linaro.org, svaidy@linux.vnet.ibm.com,
ego@linux.vnet.ibm.com, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cpufreq: governor: Be friendly towards latency-sensitive bursty workloads
Date: Tue, 27 May 2014 08:45:52 +0530 [thread overview]
Message-ID: <53840368.4030004@linux.vnet.ibm.com> (raw)
In-Reply-To: <2902116.OdbNv5KQzQ@vostro.rjw.lan>
On 05/27/2014 04:57 AM, Rafael J. Wysocki wrote:
> Hi Srivatsa,
>
> On Tuesday, May 27, 2014 02:23:38 AM Srivatsa S. Bhat wrote:
>> Cpufreq governors like the ondemand governor calculate the load on the CPU
>> periodically by employing deferrable timers. A deferrable timer won't fire
>> if the CPU is completely idle (and there are no other timers to be run), in
>> order to avoid unnecessary wakeups and thus save CPU power.
>>
>> However, the load calculation logic is agnostic to all this, and this can
>> lead to the problem described below.
>
> This is subtle enough that I need some more time to chew on it, but since the
> merge window is coming, I'm not sure when that's going to happen honestly.
>
Sure, I completely understand. Please take your time, no hurry!
Thank you very much!
Regards,
Srivatsa S. Bhat
next prev parent reply other threads:[~2014-05-27 3:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-26 20:53 [PATCH] cpufreq: governor: Be friendly towards latency-sensitive bursty workloads Srivatsa S. Bhat
2014-05-26 23:27 ` Rafael J. Wysocki
2014-05-27 3:15 ` Srivatsa S. Bhat [this message]
2014-06-02 7:33 ` Gautham R Shenoy
2014-06-02 8:15 ` Srivatsa S. Bhat
2014-06-03 5:16 ` Gautham R Shenoy
2014-06-03 5:49 ` Srivatsa S. Bhat
2014-06-03 8:18 ` Viresh Kumar
2014-06-03 9:32 ` Srivatsa S. Bhat
2014-06-03 9:39 ` Viresh Kumar
2014-06-03 10:04 ` Srivatsa S. Bhat
2014-06-03 10:08 ` Viresh Kumar
2014-06-03 10:13 ` Srivatsa S. Bhat
2014-06-03 10:16 ` Viresh Kumar
2014-06-03 10:16 ` Srivatsa S. Bhat
2014-06-07 9:55 ` Pavel Machek
2014-06-07 12:35 ` Srivatsa S. Bhat
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=53840368.4030004@linux.vnet.ibm.com \
--to=srivatsa.bhat@linux.vnet.ibm.com \
--cc=ego@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=svaidy@linux.vnet.ibm.com \
--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).