public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joseph Pingenot <trelane@digitasaru.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 16:34:14 -0500	[thread overview]
Message-ID: <20050707213414.GF16702@digitasaru.net> (raw)
In-Reply-To: <20050707210823.GA24774@isilmar.linta.de>

>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?

-Joseph

-- 
trelane@digitasaru.net--------------------------------------------------
          Graduate student in physics, Free Software developer.

  reply	other threads:[~2005-07-07 21:40 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 [this message]
2005-07-07 21:51                   ` Dominik Brodowski
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=20050707213414.GF16702@digitasaru.net \
    --to=trelane@digitasaru.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