From: Juri Lelli <Juri.Lelli@arm.com>
To: Steve Muckle <steve.muckle@linaro.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
"Rafael J . Wysocki" <rafael@kernel.org>,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
Vincent Guittot <vincent.guittot@linaro.org>,
Morten Rasmussen <morten.rasmussen@arm.com>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Patrick Bellasi <patrick.bellasi@arm.com>
Subject: Re: [PATCH 2/2] sched: cpufreq: use rt_avg as estimate of required RT CPU capacity
Date: Fri, 2 Sep 2016 10:35:49 +0100 [thread overview]
Message-ID: <20160902093549.GU9337@e106622-lin> (raw)
In-Reply-To: <20160901214851.GP5599@graphite.smuckle.net>
On 01/09/16 14:48, Steve Muckle wrote:
> On Wed, Aug 31, 2016 at 06:00:02PM +0100, Juri Lelli wrote:
> > > Another problem is that we have many semi related knobs; we have the
> > > global RT runtime limit knob, but that doesn't affect cpufreq (maybe it
> > > should)
> >
> > Maybe we could create this sort of link when using the cgroup RT
> > throttling interface as well? It should still then fit well once we
> > replace the underlying mechanism with DL reservations. And, AFAIK, the
> > interface is used by Android folks already.
>
> I'm not sure how the upper bounds can be used to infer CPU frequency...
> On my Nexus 6p (an Android device), the global RT runtime limit
> seems to be set at 950ms/1sec, the root cgroup is set to 800ms/1sec, and
> bg_non_interactive is set at 700ms/1sec.
>
Right, unfortunately. Still too coarse grained (as Thomas is also saying
in his last reply, if I read it correctly). Doesn't pay off the added
complexity I'm afraid.
next prev parent reply other threads:[~2016-09-02 9:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-26 18:40 [PATCH 0/2] utilization changes for schedutil Steve Muckle
2016-08-26 18:40 ` [PATCH 1/2] sched: cpufreq: ignore SMT when determining max cpu capacity Steve Muckle
2016-08-31 1:27 ` Rafael J. Wysocki
2016-08-31 14:34 ` Peter Zijlstra
2016-09-12 22:25 ` Rafael J. Wysocki
2016-08-26 18:40 ` [PATCH 2/2] sched: cpufreq: use rt_avg as estimate of required RT CPU capacity Steve Muckle
2016-08-31 1:31 ` Rafael J. Wysocki
2016-08-31 14:49 ` Steve Muckle
2016-08-31 14:39 ` Peter Zijlstra
2016-08-31 15:08 ` Steve Muckle
2016-08-31 16:28 ` Thomas Gleixner
2016-08-31 16:40 ` Peter Zijlstra
2016-08-31 17:00 ` Juri Lelli
2016-09-01 7:12 ` Peter Zijlstra
2016-09-01 21:48 ` Steve Muckle
2016-09-02 9:35 ` Juri Lelli [this message]
2016-09-02 12:17 ` Thomas Gleixner
2016-08-31 22:50 ` Rafael J. Wysocki
2016-09-02 8:12 ` Thomas Gleixner
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=20160902093549.GU9337@e106622-lin \
--to=juri.lelli@arm.com \
--cc=dietmar.eggemann@arm.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@kernel.org \
--cc=steve.muckle@linaro.org \
--cc=tglx@linutronix.de \
--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
Powered by JetHome