From: Viresh Kumar <viresh.kumar@linaro.org>
To: Claudio Scordino <claudio@evidence.eu.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
"Rafael J . Wysocki" <rafael.j.wysocki@intel.com>,
Patrick Bellasi <patrick.bellasi@arm.com>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Morten Rasmussen <morten.rasmussen@arm.com>,
Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Todd Kjos <tkjos@android.com>, Joel Fernandes <joelaf@google.com>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cpufreq: schedutil: rate limits for SCHED_DEADLINE
Date: Fri, 9 Feb 2018 14:10:39 +0530 [thread overview]
Message-ID: <20180209084039.GZ28462@vireshk-i7> (raw)
In-Reply-To: <197c26ba-c2a6-2de7-dffa-5b884079f746@evidence.eu.com>
On 09-02-18, 09:02, Claudio Scordino wrote:
> If I'm not wrong, at the hardware level we do have a physical rate limit (as we cannot trigger a frequency update when there is one already on-going).
> Don't know if this could somehow mitigate such effect.
Yeah, so in the worst case we will start a new freq-change right after
the previous one has finished.
--
viresh
next prev parent reply other threads:[~2018-02-09 8:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-08 17:01 Claudio Scordino
2018-02-09 3:51 ` Viresh Kumar
2018-02-09 8:02 ` Claudio Scordino
2018-02-09 8:40 ` Viresh Kumar [this message]
2018-02-09 10:36 ` Rafael J. Wysocki
2018-02-09 10:53 ` Juri Lelli
2018-02-09 11:04 ` Rafael J. Wysocki
2018-02-09 11:26 ` Juri Lelli
2018-02-09 11:37 ` Rafael J. Wysocki
2018-02-09 11:51 ` Juri Lelli
2018-02-09 12:08 ` Rafael J. Wysocki
2018-02-09 12:52 ` Juri Lelli
2018-02-09 12:56 ` Rafael J. Wysocki
2018-02-09 13:20 ` Claudio Scordino
2018-02-09 13:25 ` Juri Lelli
2018-02-09 11:14 ` Rafael J. Wysocki
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=20180209084039.GZ28462@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=claudio@evidence.eu.com \
--cc=dietmar.eggemann@arm.com \
--cc=joelaf@google.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=morten.rasmussen@arm.com \
--cc=patrick.bellasi@arm.com \
--cc=peterz@infradead.org \
--cc=rafael.j.wysocki@intel.com \
--cc=tkjos@android.com \
--cc=vincent.guittot@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
all inboxes | Powered by JetHome®