From: Michael Guntsche <mike@it-loops.com>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.25.x: Wrong CPU frequency (cpufreq table) with p4-clockmod
Date: Mon, 2 Jun 2008 07:22:44 +0200 [thread overview]
Message-ID: <f513a98ea2e03f81941beae941a63b42@localhost> (raw)
In-Reply-To: <48435CCA.5000905@gmail.com>
On Sun, 01 Jun 2008 21:36:58 -0500, Roger Heflin <rogerheflin@gmail.com>
wrote:
> Arjan van de Ven wrote:
>>
>> just as a side note.. you do realize that with p4-clockmod, your cpu is
>> still running at 1.7 GHz right? (it's just doing less work '-)
> From my testing, I believe the only thing that p4-clockmod does is
forces
> an
> idle call when it could otherwise do work on an active process, so
> fullspeed and
> idle uses *EXACTLY* the same amount of power as p4-clockmod slower speed
<snip>
Thanks for the detailed information everyone. The first time I tested this
I was under the impression that it indeed had an influence on the produced
heat of the CPU. I did a quick test this morning and of course you are
right, there is no change at all.
This is a good thing though, since it gives me an excuse to upgrade this
machine to a C2D. :)
For the time being I will just disable the cpufreq stuff since it really
does not make a difference in my case.
Kind regards,
Michael
next prev parent reply other threads:[~2008-06-02 5:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-30 13:44 2.6.25.x: Wrong CPU frequency (cpufreq table) with p4-clockmod Guntsche Michael
2008-05-30 13:57 ` Arjan van de Ven
2008-05-30 14:07 ` Guntsche Michael
2008-06-01 21:57 ` Guntsche Michael
2008-06-02 1:56 ` Arjan van de Ven
2008-06-02 2:36 ` Roger Heflin
2008-06-02 5:22 ` Michael Guntsche [this message]
2008-06-02 15:37 ` Henrique de Moraes Holschuh
2008-06-02 16:44 ` Matthew Garrett
-- strict thread matches above, loose matches on Subject: below --
2008-05-30 17:21 Guntsche Michael
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=f513a98ea2e03f81941beae941a63b42@localhost \
--to=mike@it-loops.com \
--cc=linux-kernel@vger.kernel.org \
/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.