From: Dominik Brodowski <linux@dominikbrodowski.net>
To: st3@riseup.net, Dave Jones <davej@redhat.com>,
linux-kernel@vger.kernel.org, cpufreq@lists.linux.org.uk
Subject: Re: enhanced intel speedstep feature was Re: speedstep-centrino on dothan
Date: Thu, 7 Jul 2005 23:51:34 +0200 [thread overview]
Message-ID: <20050707215134.GA25660@isilmar.linta.de> (raw)
In-Reply-To: <20050707213414.GF16702@digitasaru.net>
On Thu, Jul 07, 2005 at 04:34:14PM -0500, Joseph Pingenot wrote:
> >From Dominik Brodowski on Thursday, 07 July, 2005:
> >On Thu, Jul 07, 2005 at 03:51:17PM -0500, Joseph Pingenot wrote:
> >> >Just a latest question: can be p4-clockmod used together with
> >> >speedstep-centrino? If not, would it make any sense to patch
> >> >speedstep-centrino to use this feature too?
> >> I'm a little confused. How is this different from the ACPI CPU throttling
> >> states (/proc/acpi/processor/CPUn/limit to set, throttling to see all
> >> T-states available)?
> >T-states _tend_ to be utilized using chipset logic, while p4-clockmod is
> >done in-CPU.
> >> On my 1.5-year-old Pentium-M, frequency scaling and T-states are different
> >> beasties, and act entirely differently. I'm currently in the process of
> >> rewriting my governor's brain to deal with the two more intelligently.
> >In your case, I would care about throttling. In very most cases it actually
> >increases energy consumption, as the state being entered is technically the
> >same to ACPI C2 (IIRC), so it is only "forced" idling and only useful if
> >"forced" idling is needed to not need active cooling.
>
> Why would this cause more energy consumption?
Let's say a specific computing task needs 1s to run at 100% CPU load. The
CPU consumes 22 W at normal operation, and 7.3 W when in ACPI C2 state which
is technically equivalent to throttling. [note: these are _real_ values from
a real datasheet for a real CPU you see in common usage]
If you're at 0% CPU throttling rate, you need 22 Ws for this computing task,
if you're at 25% 24 Ws,
at 50% 29 Ws,
and at 75% that is 44 Ws for this computing task.
So for any sepcific computing task the energy consumption increases largely.
But what if the system idle otherwise?
If the CPU is put into an idle state the other time (e.g. there is no
other computing task for the CPU to do in a four-second span), it depends on
the idle state being used: if it is C2, these four seconds mean 44Ws of
energy being used; if it is C3, the CPU only needs 5.1Ws, so at 0% CPU
throttling you get 37 Ws; if it is C4, the CPU only needs 0.55Ws, so you
only get 24 Ws which is much less than the 44Ws you have at 75% throttling.
Please note that the weak spot in this calculation is the idle state the
CPU is forced to when doing idling. My investigations lead to the assumption
that it is the "Stop Grant" state on CPUs manufactored by Intel, which is
most often described by the ACPI C2 state ("Stop-Grant state"), while C3 is
"Deep Sleep State" or "Sleep State", and C4 is "Deeper Sleep State".
Dominik
next prev parent reply other threads:[~2005-07-07 21:54 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-06 9:22 speedstep-centrino on dothan st3
2005-07-06 14:06 ` Dominik Brodowski
2005-07-06 19:45 ` st3
2005-07-06 16:30 ` Pedro Ramalhais
2005-07-06 19:58 ` Bill Davidsen
2005-07-06 21:11 ` Dave Jones
2005-07-06 21:55 ` st3
2005-07-07 20:00 ` enhanced intel speedstep feature was " st3
2005-07-07 20:06 ` Dave Jones
2005-07-07 20:22 ` st3
2005-07-07 20:40 ` Dave Jones
2005-07-07 20:51 ` Joseph Pingenot
2005-07-07 21:08 ` Dominik Brodowski
2005-07-07 21:34 ` Joseph Pingenot
2005-07-07 21:51 ` Dominik Brodowski [this message]
2005-07-07 21:10 ` Dominik Brodowski
2005-07-07 21:22 ` st3
2005-07-07 21:29 ` Dominik Brodowski
2005-07-07 21:59 ` st3
2005-07-08 5:10 ` Dominik Brodowski
2005-07-08 8:58 ` st3
2005-07-08 10:59 ` Nikolay Pelov
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=20050707215134.GA25660@isilmar.linta.de \
--to=linux@dominikbrodowski.net \
--cc=cpufreq@lists.linux.org.uk \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=st3@riseup.net \
/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