From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
Leo Yan <leo.yan@linaro.org>,
Brendan Jackman <brendan.jackman@arm.com>,
Lists linaro-kernel <linaro-kernel@lists.linaro.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux PM <linux-pm@vger.kernel.org>,
Amit Kucheria <amit.kucheria@linaro.org>
Subject: Re: [PATCH] cpufreq: dt: Set default policy->transition_delay_ns
Date: Wed, 28 Jun 2017 22:52:53 +0200 [thread overview]
Message-ID: <3617293.cCXa2uXImB@aspire.rjw.lan> (raw)
In-Reply-To: <20170628041455.GE29665@vireshk-i7>
On Wednesday, June 28, 2017 09:44:55 AM Viresh Kumar wrote:
> On 27-06-17, 18:08, Rafael J. Wysocki wrote:
> > On Tue, Jun 27, 2017 at 6:20 AM, Viresh Kumar <viresh.kumar@linaro.org> wrote:
> > > @Rafael: Will it be fine to lower down the value of LATENCY_MULTIPLIER?
> >
> > We can do that, but then I think we need to compensate for the change
> > in the old governors code or there may be surprises.
>
> Why shouldn't we change the value of LATENCY_MULTIPLIER for old
> governors as well? They use the same calculations and the sampling
> rate there is also this bad (like rate_limit_us).
On some systems. On other systems it isn't.
> If we aren't going to change that for old governors, then we can
> create a local version of LATENCY_MULTIPLIER for schedutil I believe.
OK, so at least for intel_pstate and acpi-cpufreq we want a 10 ms default
which is what we have currently.
If you want to rework all that, make sure you preserve that.
Thanks,
Rafael
prev parent reply other threads:[~2017-06-28 21:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-22 5:10 [PATCH] cpufreq: dt: Set default policy->transition_delay_ns Viresh Kumar
2017-05-22 10:45 ` Brendan Jackman
2017-05-22 10:55 ` Viresh Kumar
2017-05-22 11:17 ` Leo Yan
2017-05-22 11:27 ` Viresh Kumar
2017-06-27 0:15 ` Rafael J. Wysocki
2017-06-27 4:20 ` Viresh Kumar
2017-06-27 16:08 ` Rafael J. Wysocki
2017-06-28 4:14 ` Viresh Kumar
2017-06-28 20:52 ` Rafael J. Wysocki [this message]
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=3617293.cCXa2uXImB@aspire.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=amit.kucheria@linaro.org \
--cc=brendan.jackman@arm.com \
--cc=leo.yan@linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.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