From: Dominik Brodowski <linux@brodo.de>
To: Viktor Radnai <efti@gotiao.com>
Cc: cpufreq@www.linux.org.uk
Subject: Re: Feature request
Date: Thu, 28 Aug 2003 15:50:36 +0200 [thread overview]
Message-ID: <20030828135036.GA17216@brodo.de> (raw)
In-Reply-To: <3F4CE772.9090605@gotiao.com>
On Thu, Aug 28, 2003 at 03:16:34AM +1000, Viktor Radnai wrote:
> Dominik Brodowski wrote:
> >Oh well, so users want to use 150 MHz instead of 1600 MHz now...
> My laptop is still quite responsive at 150MHz and anything that lets me
> conserve battery power when the performance isn't needed is worth
> trying. After all, this is the very purpose of frequency scaling. It
> doesn't really matter how fast the kernel executes idle loops ;)
Well, does your computer do some real "idling" - e.g. ACPI C-States [C2 and
above] or APM "halt"? If so, then you don't need any throttling - it saves
approximately the same amount of energy.
> >worthy of discussion for 2.7.
> That would be great, too bad that it won't happen sooner. In the
> meantime, do you think that the method described below is an acceptable
> way of saving power or do you foresee any potential problems /
> instability as a result of this?
>
> If you think that this is a workable method then I might hack one of the
> userspace frequency scaling utilities to support this method.
As most systems support either ACPI-C-States or APM "halt" and these methods
are as "good" for power saving, I don't see a reason to implement this at
the moment.
Dominik
next prev parent reply other threads:[~2003-08-28 13:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-23 7:51 Pentium 4m kernel 2.4.21 Martin Klinkigt (multimedia-test)
2003-08-23 9:49 ` Viktor Radnai
2003-08-23 10:50 ` Feature request (was: Pentium 4m kernel 2.4.21) Viktor Radnai
2003-08-26 23:10 ` Dominik Brodowski
2003-08-27 17:16 ` Feature request Viktor Radnai
2003-08-28 13:50 ` Dominik Brodowski [this message]
2003-08-28 16:04 ` Daniel Thor Kristjansson
2003-09-19 17:17 ` Feature request (was: Pentium 4m kernel 2.4.21) Jan Rychter
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=20030828135036.GA17216@brodo.de \
--to=linux@brodo.de \
--cc=cpufreq@www.linux.org.uk \
--cc=efti@gotiao.com \
/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