cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Stezenbach <js@linuxtv.org>
To: Dominik Brodowski <linux@dominikbrodowski.net>
Cc: Adrian Bunk <bunk@stusta.de>, Andi Kleen <ak@suse.de>,
	Dave Jones <davej@redhat.com>,
	Dmitry Torokhov <dtor_core@ameritech.net>,
	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: Mon, 27 Feb 2006 00:37:45 +0100	[thread overview]
Message-ID: <20060226233745.GA6804@linuxtv.org> (raw)
In-Reply-To: <20060226205513.GA26486@isilmar.linta.de>

On Sun, Feb 26, 2006, Dominik Brodowski wrote:
> On Sun, Feb 26, 2006 at 09:39:41PM +0100, Johannes Stezenbach wrote:
> > 
> > Do you have the numbers for a Pentium(R) 4 HT? (I couldn't find
> > anything substantial with google.) Especially C2 vs. C2 + throttling?
> > Because the way I remember having read somewhere, the idle
> > (C2) power consumption of the P4 is significantly higher
> > than with the Pentium(R) M.
> 
> Unfortunately, I do not have these numbers present. You can check the
> processor specification sheets at Intel's website, though.

Went to the Intel(R) website, searched for half an hour, found many
docs but none that gives useful information about this, gave up. :-(

> > > So: P4-clockmod style throttling only makes sense if either
> > > 
> > > a) the idle handler does not enter the Stop-Grant state (C2) efficiently, or
> > 
> > Maybe my previous mails were not clear enough: The goal is to
> > reduce idle power consumption (and by that fan noise). The PC
> > is running but is idle, e.g just listening for possible incoming
> > jabber messages or whatever.
> 
> Most probably, the idle handler can't make use of the Stop-Grant state (C2)
> here, so this is case a) noted above.

Hm.

Thanks,
Johannes

  reply	other threads:[~2006-02-26 23:37 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 [this message]
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

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=20060226233745.GA6804@linuxtv.org \
    --to=js@linuxtv.org \
    --cc=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=linux@dominikbrodowski.net \
    --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