All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Adrian Bunk <bunk@kernel.org>
Cc: Arjan van de Ven <arjan@infradead.org>,
	S K <nospamnoham@gmail.com>, Zhao Yakui <yakui.zhao@intel.com>,
	Thomas Renninger <trenn@suse.de>,
	Alan Jenkins <alan-jenkins@tuffmail.co.uk>,
	linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: cpufreq doesn't seem to work in Intel Q9300
Date: Mon, 11 Aug 2008 15:07:34 +0100	[thread overview]
Message-ID: <20080811140734.GA27959@srcf.ucam.org> (raw)
In-Reply-To: <20080811140206.GB3338@cs181140183.pp.htv.fi>

On Mon, Aug 11, 2008 at 05:02:06PM +0300, Adrian Bunk wrote:

> This statement is only true for HPC environments and when you measure 
> Watts per work done.
> 
> But if you have some desktop or server with a load that is determined by 
> when it gets used, then p4-clockmod can actually save energy when the 
> computer is not under high load or even idle.
> 
> Or do I miss anything?

On modern hardware, the C states will win you more than downclocking the 
processor would.

-- 
Matthew Garrett | mjg59@srcf.ucam.org

  reply	other threads:[~2008-08-11 14:07 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-03 10:00 cpufreq doesn't seem to work in Intel Q9300 S K
2008-08-03 10:31 ` none
2008-08-04  5:06   ` S K
2008-08-07  9:35     ` S K
2008-08-07 19:24       ` Alan Jenkins
2008-08-08  1:32       ` Zhao Yakui
2008-08-08  4:53         ` S K
2008-08-08  8:41           ` Alan Jenkins
2008-08-08 10:10             ` S K
2008-08-08 10:43               ` S K
2008-08-08 12:30                 ` Thomas Renninger
2008-08-08 18:23                   ` S K
2008-08-09 18:59                     ` Thomas Renninger
2008-08-09 18:59                       ` Thomas Renninger
2008-08-09 19:30                       ` Thomas Renninger
2008-08-09 19:30                         ` Thomas Renninger
2008-08-10  8:28                       ` S K
2008-08-11  1:33                         ` Zhao Yakui
2008-08-11  4:44                           ` S K
2008-08-11  5:24                             ` Zhao Yakui
2008-08-11  5:24                               ` S K
2008-08-11  7:00                                 ` Alan Cox
2008-08-11 10:55                               ` Andi Kleen
2008-08-11 13:15                                 ` S K
2008-08-11 13:23                                   ` Andi Kleen
2008-08-12  5:43                                     ` S K
2008-08-11 11:22                             ` Arjan van de Ven
2008-08-11 11:38                               ` Alexey Dobriyan
2008-08-11 11:53                                 ` Matthew Garrett
2008-08-11 14:02                               ` Adrian Bunk
2008-08-11 14:07                                 ` Matthew Garrett [this message]
2008-08-11 14:12                                   ` Arjan van de Ven
2008-08-11 14:11                                 ` Arjan van de Ven
2008-08-11 16:03                                   ` Adrian Bunk
2008-08-11 16:20                                     ` Arjan van de Ven
2008-08-11 16:28                                       ` Adrian Bunk
2008-08-11 16:44                                         ` Arjan van de Ven
2008-08-12 19:27                                           ` Adrian Bunk
2008-08-11 19:33                                   ` Dominik Brodowski
2008-08-11 23:58                                     ` Arjan van de Ven
2008-08-12 19:03                                       ` Dominik Brodowski
2008-08-12 19:59                                         ` Arjan van de Ven

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=20080811140734.GA27959@srcf.ucam.org \
    --to=mjg59@srcf.ucam.org \
    --cc=alan-jenkins@tuffmail.co.uk \
    --cc=arjan@infradead.org \
    --cc=bunk@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nospamnoham@gmail.com \
    --cc=trenn@suse.de \
    --cc=yakui.zhao@intel.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.