From: Kevin Hilman <khilman@ti.com>
To: Antti P Miettinen <amiettinen@nvidia.com>
Cc: davej@redhat.com, pavel@ucw.cz, rjw@sisk.pl, len.brown@intel.com,
j-pihet@ti.com, markgross@thegnar.org, cpufreq@vger.kernel.org,
linux-pm@lists.linux-foundation.org
Subject: Re: [linux-pm] [PATCH 0/2] RFC: CPU frequency max as PM QoS param
Date: Wed, 15 Feb 2012 17:06:40 -0800 [thread overview]
Message-ID: <87d39fk2n3.fsf@ti.com> (raw)
In-Reply-To: <1326976559-4009-1-git-send-email-amiettinen@nvidia.com> (Antti P. Miettinen's message of "Thu, 19 Jan 2012 14:35:57 +0200")
Hello,
Antti P Miettinen <amiettinen@nvidia.com> writes:
> This is a continuation to "RFC: CPU frequency min as PM QoS param"
> patchset. This patchset adds CPU frequency maximum as a PM QoS
> parameter and modifies CPU frequncy core to enforce the limit. CPU
> frequency ceiling can be used to improve the energy efficiency of
> workloads that would cause the cpufreq governors to enforce an
> unnecessarily high operating point. In other words, CPU frequency
> maximum can act as an energy efficiency level request.
>
> Tested on Dell E6420 with the ACPI cpufreq driver against Ubuntu
> 3.2. Patches are against linux-next, compile tested.
I know there were some earlier discussions about the usefulness of a max
frequency QoS parameter, so I wanted to throw in a reason to include max
as well as min frequency parameters.
IMO, having a max frequency QoS parameter would be very useful from a
thermal perspective.
There are some ongoing projects in the PM working group at Linaro that
are exploring plugins to the thermal framework that implment a "cooling
device" by capping CPU frequency. Having a QoS parameter do do this
would be the logical interface.
I also agree with some earlier requests that these should probably be
per-CPU instead of global. That would make it simple to cap frequency
of one cluster while leaving another alone.
Kevin
next prev parent reply other threads:[~2012-02-16 1:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-19 12:35 [PATCH 0/2] RFC: CPU frequency max as PM QoS param Antti P Miettinen
2012-01-19 12:35 ` [PATCH 1/2] PM QoS: Add CPU frequency maximum " Antti P Miettinen
2012-01-19 12:35 ` [PATCH 2/2] cpufreq: Enforce PM QoS maximum frequency Antti P Miettinen
2012-02-16 1:06 ` Kevin Hilman [this message]
2012-02-17 3:04 ` [PATCH 0/2] RFC: CPU frequency max as PM QoS param mark gross
2012-02-17 8:12 ` [linux-pm] " Valentin, Eduardo
2012-02-20 10:00 ` Antti P Miettinen
[not found] ` <CAGF5oy-64J3vMKvzY=NvdV-m8_wFo=NGZANF_cnVm-iq0s-wZQ@mail.gmail.com>
[not found] ` <20120221145632.GA2840@envy17>
[not found] ` <87linw5aod.fsf@ti.com>
[not found] ` <20120225174449.GA17141@envy17>
2012-02-27 10:17 ` [linux-pm] " Pihet-XID, Jean
2012-02-27 11:00 ` Antti P Miettinen
[not found] ` <877gz8wcud.fsf@ti.com>
2012-02-27 15:04 ` Antti Miettinen
2012-02-28 0:56 ` [linux-pm] " mark gross
2012-02-28 9:37 ` Antti P Miettinen
2012-03-04 22:46 ` Rafael J. Wysocki
2012-03-06 12:23 ` Antti P Miettinen
2012-03-06 14:37 ` Dave Jones
2012-03-07 6:38 ` Antti P Miettinen
2012-03-07 16:59 ` Dave Jones
2012-03-07 18:08 ` Antti P Miettinen
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=87d39fk2n3.fsf@ti.com \
--to=khilman@ti.com \
--cc=amiettinen@nvidia.com \
--cc=cpufreq@vger.kernel.org \
--cc=davej@redhat.com \
--cc=j-pihet@ti.com \
--cc=len.brown@intel.com \
--cc=linux-pm@lists.linux-foundation.org \
--cc=markgross@thegnar.org \
--cc=pavel@ucw.cz \
--cc=rjw@sisk.pl \
/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