public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Steve Muckle <steve.muckle@linaro.org>
Cc: 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 11:24:16 +0200	[thread overview]
Message-ID: <20160523092416.GE15728@worktop.ger.corp.intel.com> (raw)
In-Reply-To: <20160522204252.GH15383@graphite.smuckle.net>

On Sun, May 22, 2016 at 01:42:52PM -0700, Steve Muckle wrote:

> > 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.

Oh agreed, completely platform dependent. 'Luckily' all this cpuidle is
already very platform dependent.

> It is also true that there is power spent going to fmin (and then
> perhaps restoring the frequency when idle ends) which will be in part a
> function of how slow the frequency change operation is on that platform.

Agreed.

> I think Daniel Lezcano (added) was exploring the idea of having cpuidle
> drivers take the expected idle duration and potentially communicate to
> cpufreq to reduce the frequency depending on a platform-specific
> cost/benefit analysis.

Right; that's along the lines I was thinking. If the idle guestimate and
the idle QoS both allow (ie. it wins on power and doesn't violate
wake-up latency) muck with DVSF on the idle path.

      parent reply	other threads:[~2016-05-23  9:24 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
2016-05-23  9:24             ` Peter Zijlstra
2016-05-23  9:24           ` Peter Zijlstra [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=20160523092416.GE15728@worktop.ger.corp.intel.com \
    --to=peterz@infradead.org \
    --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=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