From: Dave Jones <davej@redhat.com>
To: Rick Nas <rick.nas@gmail.com>
Cc: cpufreq@lists.linux.org.uk
Subject: Re: cpufreq with ondemand/p4-clockmod crashes kernel on Celeron-D 325
Date: Mon, 5 Dec 2005 13:37:05 -0500 [thread overview]
Message-ID: <20051205183705.GG12664@redhat.com> (raw)
In-Reply-To: <12aa0420512041411q1aab21d3o3bbddd38cc8140b4@mail.gmail.com>
On Sun, Dec 04, 2005 at 11:11:10PM +0100, Rick Nas wrote:
> Yeah, I gathered that from recent discussions on this list. But it seems
> strange to me, if clock modulation has a thermal effect, shouldn't it have a
> power effect as well? I mean, the heat is generated by the current right,
> less heat => less current??
>
> Anyway, I also read that the issue has been explained on this list a couple
> of times already, so I guess you're right.
With clock modulation, you're still running the CPU at the same amount
of current, you're just not doing useful work every clock cycle.
If you're only doing something once every four clocks, it'll take
4 times as long to finish that workload. So you don't save any
battery because you're increasing the runtime. You get thermal wins
because of the idle slots you're introducing, where the CPU isn't doing
anything.
Pretty pictures should explain it if the above still seems odd..
no modulation:
____
_| |_________________
with modulation:
_ _ _ _
_| |___| |___| |___| |___
The 'level' part of the diagrams indicate the CPU idling.
What an edge occurs, it's doing useful work, and generating heat.
Dave
prev parent reply other threads:[~2005-12-05 18:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-18 21:25 cpufreq with ondemand/p4-clockmod crashes kernel on Celeron-D 325 Rick Nas
2005-12-04 17:18 ` Dominik Brodowski
2005-12-04 22:11 ` Rick Nas
2005-12-05 18:37 ` Dave Jones [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=20051205183705.GG12664@redhat.com \
--to=davej@redhat.com \
--cc=cpufreq@lists.linux.org.uk \
--cc=rick.nas@gmail.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.