From: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
To: Steve Muckle <steve.muckle@linaro.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Shilpasri G Bhat <shilpa.bhat@linux.vnet.ibm.com>,
"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
Subject: Re: [RFC PATCH] Increase in idle power with schedutil
Date: Mon, 23 May 2016 10:00:04 +0100 [thread overview]
Message-ID: <20160523090004.GA21186@red-moon> (raw)
In-Reply-To: <20160522204252.GH15383@graphite.smuckle.net>
On Sun, May 22, 2016 at 01:42:52PM -0700, Steve Muckle wrote:
> On Sun, May 22, 2016 at 12:39:12PM +0200, Peter Zijlstra wrote:
> > On Fri, May 20, 2016 at 05:53:41PM +0530, Shilpasri G Bhat wrote:
> > >
> > > 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.
> >
> > So does it actually matter what the frequency is when you idle? Isn't
> > the whole thing clock gated anyway?
> >
> > Because this seems to generate contradictory requirements, on the one
> > hand we want to stay idle as long as possible while on the other hand
> > you seem to want to clock down while idle, which requires not being
> > idle.
> >
> > If it matters; should not your idle state muck explicitly set/restore
> > frequency?
>
> AFAIK this is very platform dependent. Some will waste more power than
> others when a CPU idles above fmin due to things like resource (bus
> bandwidth, shared cache freq etc) voting.
It is also related to static leakage power that depends on the operating
voltage (ie higher operating frequencies require higher voltage) so in a
way scaling frequency before going idle may not be effective if voltage
does not scale too in turn.
Lorenzo
next prev parent reply other threads:[~2016-05-23 8:59 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
[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 [this message]
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=20160523090004.GA21186@red-moon \
--to=lorenzo.pieralisi@arm.com \
--cc=akshay.adiga@linux.vnet.ibm.com \
--cc=daniel.lezcano@linaro.org \
--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=shilpa.bhat@linux.vnet.ibm.com \
--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).