From: Willy Tarreau <w@1wt.eu>
To: Pavel Machek <pavel@ucw.cz>
Cc: Matthew Garrett <mjg59@srcf.ucam.org>,
"Tippett, Matthew" <Matthew.Tippett@amd.com>,
"Langsdorf, Mark" <mark.langsdorf@amd.com>,
lenb@kernel.org, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org, "Li, Samuel" <Samuel.Li@amd.com>
Subject: Re: [PATCH]AC/DC notifier
Date: Sun, 16 Aug 2009 09:40:08 +0200 [thread overview]
Message-ID: <20090816074008.GA11624@1wt.eu> (raw)
In-Reply-To: <20090814163233.GC1626@ucw.cz>
On Fri, Aug 14, 2009 at 06:32:33PM +0200, Pavel Machek wrote:
> On Wed 2009-08-12 01:55:32, Matthew Garrett wrote:
> > On Tue, Aug 11, 2009 at 08:51:49PM -0400, Tippett, Matthew wrote:
> >
> > > From a graphics perspective (your area of expertise), this will allow KMS
> > > drivers to do some more intelligent actions based on the ac/dc state.
> > > Some examples of this could be improving the power consumption of the
> > > graphics hardware through adapting clock memory/engine settings for
> > > reduced power consumption, reducing refresh rate of the display to reduce
> > > scanout memory access, adjusting backlight brightness, etc.
> >
> > Right. As you say, my concern is that most of this should belong in
> > userspace. Where we risk hardware damage there's an obvious argument for
> > doing this in kernel, but we should ensure that that's limited to
> > whatever coarse-grain handling is absolutely required rather than doing
> > things like touching display brightness.
>
> Yep... Some may want to save power even when AC is online -- like when
> running on UPS. Some may want max performmance even on battery.
Wholeheartly agreed. IMHO, there's absolutely no relation between power
source and the expected performance. It's really frustrating when your
laptop becomes a snail on battery, as well as it's annoying to hear it
sound like a hairdryer when plugged to mains. This should only be the
user's choice. Mine automatically adjusts its frequency on demand,
regardless of the power source, which provides me with the best
experience. I think that all the tricks used to save power when running
on battery were invented by laptop makers to artificially show longer
lasting eventhough the machine sometimes becomes barely usable. For
instance, some of them dim the backlight so that you can't read anything
in full light, so you need a power prolongator to use them outside !
Also, with the new trend of laptops making use of huge power-hungry 3D
graphic chips which suck all the juice out of your battery in less than
two hours doing nothing, you'd better run at full speed when on battery
to save energy for CPU-bound tasks, because eventhough the CPU eats more
power, you significantly reduce the run time, thus the static consumption
(GPU, backlight, hard disk, ...).
Willy
next prev parent reply other threads:[~2009-08-16 7:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <FFAE0590FF35E441901B67BD8BA62E950245ABD9@storexmb3.amd.com>
2009-08-12 0:55 ` [PATCH]AC/DC notifier Matthew Garrett
2009-08-14 16:32 ` [PATCH][ACPI] AC/DC notifier Pavel Machek
2009-08-16 7:40 ` Willy Tarreau [this message]
2009-10-06 14:53 ` [PATCH]AC/DC notifier Tippett, Matthew
2009-10-07 7:31 ` [PATCH][ACPI] AC/DC notifier Pavel Machek
2009-10-07 8:16 ` Dave Airlie
2009-10-07 14:05 ` [PATCH]AC/DC notifier Matthew Garrett
2009-10-07 17:00 ` [PATCH][ACPI] AC/DC notifier Tippett, Matthew
2009-08-11 20:15 Mark Langsdorf
2009-08-11 23:49 ` [PATCH]AC/DC notifier Matthew Garrett
2009-10-06 17:56 ` Len Brown
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=20090816074008.GA11624@1wt.eu \
--to=w@1wt.eu \
--cc=Matthew.Tippett@amd.com \
--cc=Samuel.Li@amd.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.langsdorf@amd.com \
--cc=mjg59@srcf.ucam.org \
--cc=pavel@ucw.cz \
/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).