All of lore.kernel.org
 help / color / mirror / Atom feed
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

  reply	other threads:[~2003-08-28 13:50 UTC|newest]

Thread overview: 43+ 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
  -- strict thread matches above, loose matches on Subject: below --
2005-04-14 16:50 feature request `VL
2005-04-14 18:18 ` Taylor, Grant
2005-04-14 18:37   ` Leonardo Rodrigues Magalhães
2005-04-14 18:52     ` Taylor, Grant
2008-09-09  9:49 Feature Request l5ynlwlcyku9kvaqc2jf.j.HadVabVobs
2010-02-09  8:43 Stefan *St0fF* Huebner
2010-02-09 12:28 ` Michael Tokarev
2010-02-09 14:19   ` Stefan Hübner
2012-10-16 11:36 feature request Angelo Borsotti
2012-10-16 12:15 ` Andrew Ardill
2012-10-16 17:27   ` Angelo Borsotti
2012-10-16 23:30     ` Sitaram Chamarty
2012-10-17  0:00     ` Andrew Ardill
2012-10-16 13:34 ` Christian Thaeter
2013-02-18 18:52 Jay Townsend
2013-02-18 19:54 ` James Nylen
2013-02-18 20:45   ` Jeff King
2013-02-19  3:26     ` Drew Northup
2013-02-19 22:27     ` Shawn Pearce
2016-10-27 21:55 John Rood
2016-10-27 22:01 ` Stefan Beller
2016-10-27 22:05   ` John Rood
2016-10-27 22:24     ` John Rood
2016-10-27 22:27       ` Junio C Hamano
2016-10-27 22:48         ` John Rood
2016-10-27 22:51           ` Junio C Hamano
2016-10-27 23:16             ` John Rood
2016-10-27 22:30 ` Stefan Beller
2016-10-27 22:44   ` John Rood
2016-10-27 22:46     ` Junio C Hamano
2016-10-27 23:24     ` David Lang
2016-10-28  8:49       ` Johannes Schindelin
2016-10-28 12:54       ` Philip Oakley
2024-06-20 12:58 Feature Request Clement Sello Tsetsa
2024-06-20 13:29 ` rsbecker

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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.