From: Len Brown <lenb@kernel.org>
To: Igor.Stoppa@nokia.com
Cc: linux-pm@lists.osdl.org, linux-kernel@vger.kernel.org,
linux-acpi@vger.kernel.org
Subject: RE: [linux-pm] RFC: /sys/power/policy_preference
Date: Thu, 17 Jun 2010 15:00:15 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.00.1006171445010.4214@localhost.localdomain> (raw)
In-Reply-To: <D32AB456855CBD4987499F68AFA421F4299A56E336@NOK-EUMSG-02.mgdnok.nokia.com>
On Thu, 17 Jun 2010, Igor.Stoppa@nokia.com wrote:
> i do understand that you are mostly targetting acpi based systems,
> but even there, based on static leaks, it might not be always true
> that lower frequencies are correlated to higher power savings
> (or maybe i have misunderstood your draft - i am not so fluent in acpi)
Right, my assertion is that ondemand deals only with P-states,
where, by defintion, the deeper the P-state the lower the voltage,
the higher the efficiency.
I assume that ondemand is not used to enable T-states
where the clock is throttled w/o lowering the voltage.
I put a note to try to make that clear under
max_powersave:
"ondemand: min P-state (do not invoke T-states)"
Of course it is also possible for a processor to do a poor job
implementing P-states and a great job optimizing idle states
such that race to idle were always a win. However, on such
a processor it would make more sense to simply disable P-states.
> > it is likely
> > that some users would want to use "powersave" when on
> > battery and perhaps shift to "performance" on A/C.
>
> if we consider also the thermal envelope and the fact that "performance"
> might steal power from a charging battery, even ton A/C it might not be
> possible to settle down in one state permanently.
>
> Or do you expect other mechanisms to intervene?
Typical laptop BIOS commonly implement a scheme where
they maximize performance on AC and bias towards saving energy
on DC.
That, of course, is just one example use-model.
Here Linux user-space can choose whatever policy
makes sense for them at run-time.
cheers,
-Len Brown, Intel Open Source Technology Center
next prev parent reply other threads:[~2010-06-17 19:00 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-16 21:05 RFC: /sys/power/policy_preference Len Brown
2010-06-16 22:12 ` Jason Chagas
2010-06-17 18:44 ` Len Brown
2010-06-17 6:03 ` [linux-pm] " Igor.Stoppa
2010-06-17 19:00 ` Len Brown [this message]
2010-06-17 16:14 ` Victor Lowther
2010-06-17 19:02 ` Len Brown
2010-06-17 22:23 ` Victor Lowther
2010-06-18 5:56 ` Len Brown
2010-06-18 11:55 ` Victor Lowther
2010-06-19 15:17 ` Vaidyanathan Srinivasan
2010-06-19 19:04 ` Rafael J. Wysocki
2010-06-17 20:48 ` Mike Chan
2010-06-18 6:25 ` Len Brown
2010-06-21 20:10 ` [linux-pm] " Dipankar Sarma
2010-09-28 16:17 ` x86_energy_perf_policy.c Len Brown
2010-10-23 4:40 ` [PATCH] tools: add x86_energy_perf_policy to program MSR_IA32_ENERGY_PERF_BIAS Len Brown
[not found] ` <alpine.LFD.2.00.1010230035360.29399@localhost.localdomain>
2010-10-27 3:23 ` Andrew Morton
[not found] ` <20101026202307.c028e26c.akpm@linux-foundation.org>
2010-10-27 6:01 ` Ingo Molnar
[not found] ` <20101027060139.GB5603@elte.hu>
2010-10-27 11:43 ` Arnaldo Carvalho de Melo
2010-11-15 16:07 ` [PATCH RESEND] tools: add power/x86/x86_energy_perf_policy " Len Brown
[not found] ` <alpine.LFD.2.00.1011151103280.2939@x980>
2010-11-17 11:35 ` Andi Kleen
[not found] ` <8739r0rxlz.fsf@basil.nowhere.org>
2010-11-22 20:13 ` Len Brown
[not found] ` <alpine.LFD.2.00.1011221348200.19247@x980>
2010-11-22 20:33 ` Andi Kleen
[not found] ` <20101122203359.GD21836@basil.fritz.box>
2010-11-23 4:48 ` Len Brown
2010-11-24 5:31 ` [PATCH v2] tools: create power/x86/x86_energy_perf_policy Len Brown
[not found] ` <alpine.LFD.2.00.1011240028470.20657@x980>
2010-11-25 5:52 ` Chen Gong
[not found] ` <4CEDF9BB.9030002@linux.intel.com>
2010-11-25 8:59 ` Chen Gong
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=alpine.LFD.2.00.1006171445010.4214@localhost.localdomain \
--to=lenb@kernel.org \
--cc=Igor.Stoppa@nokia.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.osdl.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