From: Andi Kleen <ak@suse.de>
To: dtor_core@ameritech.net
Cc: Matt Mackall <mpm@selenic.com>, Dave Jones <davej@redhat.com>,
Adrian Bunk <bunk@stusta.de>,
davej@codemonkey.org.uk,
Zwane Mwaikambo <zwane@commfireservices.com>,
Samuel Masham <samuel.masham@gmail.com>,
Jan Engelhardt <jengelh@linux01.gwdg.de>,
linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>,
cpufreq@lists.linux.org.uk
Subject: Re: Status of X86_P4_CLOCKMOD?
Date: Tue, 28 Feb 2006 23:22:01 +0100 [thread overview]
Message-ID: <200602282322.03316.ak@suse.de> (raw)
In-Reply-To: <d120d5000602281339h777a9b73nb95bf6b6b5ee90c9@mail.gmail.com>
On Tuesday 28 February 2006 22:39, Dmitry Torokhov wrote:
> On 2/28/06, Dominik Brodowski <linux@dominikbrodowski.net> wrote:
> > On Tue, Feb 28, 2006 at 03:26:32PM -0600, Matt Mackall wrote:
> > > > So even if the battery lasts longer, you don't have anything of it, 'cause
> > > > the CPU can even compute _less_ in this longer time-span. Remember that
> > > > idling doesn't count...
> > >
> > > Which is different from other power-saving modes how? If it means I
> > > can read my email longer on the plane, it's a power-saving mode.
> >
> > But you can't... [*]
> ...
> > [*] unless the idling algorithm is broken and does not enter C2-type idle
> > states.
>
> Or box does not support anything but C1.
There are quite advanced forms of C1 around.
And I would expect even old style dumb C1 to save more than throttling.
-Andi
prev parent reply other threads:[~2006-02-28 22:22 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060214152218.GI10701@stusta.de>
[not found] ` <20060222024438.GI20204@MAIL.13thfloor.at>
[not found] ` <20060222031001.GC4661@stusta.de>
[not found] ` <200602212220.05642.dtor_core@ameritech.net>
2006-02-23 19:59 ` Status of X86_P4_CLOCKMOD? Adrian Bunk
2006-02-23 20:41 ` Dave Jones
2006-02-23 23:15 ` Andi Kleen
2006-02-23 23:33 ` Adrian Bunk
2006-02-23 23:55 ` Andi Kleen
2006-02-24 2:39 ` Adrian Bunk
2006-02-24 2:42 ` Andi Kleen
2006-02-24 17:33 ` Adrian Bunk
2006-02-25 1:57 ` Johannes Stezenbach
2006-02-25 4:24 ` Dave Jones
2006-02-25 12:53 ` Johannes Stezenbach
2006-02-27 21:17 ` Wes Felter
2006-02-25 4:27 ` Andi Kleen
2006-02-25 12:53 ` Adrian Bunk
2006-02-25 13:28 ` Dominik Brodowski
2006-02-26 11:12 ` Pavel Machek
2006-02-26 20:39 ` Johannes Stezenbach
2006-02-26 20:55 ` Dominik Brodowski
2006-02-26 23:37 ` Johannes Stezenbach
2006-02-25 13:36 ` Andi Kleen
2006-02-25 13:05 ` Johannes Stezenbach
2006-02-28 19:46 ` Matt Mackall
2006-02-28 20:09 ` Dave Jones
2006-02-28 20:19 ` Dmitry Torokhov
2006-02-28 20:47 ` Matt Mackall
2006-02-28 20:57 ` Dominik Brodowski
2006-02-28 21:26 ` Matt Mackall
2006-02-28 21:34 ` Dominik Brodowski
2006-02-28 21:39 ` Dmitry Torokhov
2006-02-28 22:22 ` Andi Kleen [this message]
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=200602282322.03316.ak@suse.de \
--to=ak@suse.de \
--cc=akpm@osdl.org \
--cc=bunk@stusta.de \
--cc=cpufreq@lists.linux.org.uk \
--cc=davej@codemonkey.org.uk \
--cc=davej@redhat.com \
--cc=dtor_core@ameritech.net \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.com \
--cc=samuel.masham@gmail.com \
--cc=zwane@commfireservices.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