cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Bidewell <mark.bidewell@alumni.clemson.edu>
To: ivor@ivor.org
Cc: cpufreq@lists.linux.org.uk
Subject: Re: Possible CPUFreq governor
Date: Wed, 27 Apr 2005 08:30:45 -0400	[thread overview]
Message-ID: <426F85F5.7010700@alumni.clemson.edu> (raw)
In-Reply-To: <46736.141.228.156.225.1114600117.squirrel@www.difo.com>

You are correct, The primary differences are that
1)  the clock modulation only cuts in after dangerous temperatures have 
been detected.  This code prevents those high temperatures.
2)  This code uses the OS Scheduler to make targeted performance cuts on 
certain applications.  This reduces the performance impact of throttling 
to non-interactive processes.

>I think the idea is to reduce cpuspeed, with the intention of having the side
>effect of reducing temperature. Rather than to throttle based on temperature
>(I may be wrong). I believe P4's will throttle themselves automatically when
>they get too hot anyway.
>
>Cheers,
>Ivor.
>
>
>
>  
>

  reply	other threads:[~2005-04-27 12:30 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-26 23:39 Possible CPUFreq governor Mark Bidewell
2005-04-27 10:53 ` Bruno Ducrot
2005-04-27 11:02   ` Bruno Ducrot
2005-04-27 11:08   ` Ivor Hewitt
2005-04-27 12:30     ` Mark Bidewell [this message]
2005-04-27 14:07       ` Bruno Ducrot
2005-04-27 16:20         ` Mark Bidewell
2005-04-27 17:38           ` Bruno Ducrot
2005-04-27 18:18             ` Mark Bidewell
2005-04-27 19:04               ` Bruno Ducrot
2005-05-02 12:51                 ` Mark Bidewell
2005-04-27 12:25   ` Mark Bidewell
2005-04-27 13:54     ` Bruno Ducrot
2005-04-27 16:10       ` Mark Bidewell
2005-04-27 17:03         ` Bruno Ducrot
2005-04-27 17:19           ` Mark Bidewell
2005-04-27 17:45             ` Bruno Ducrot
  -- strict thread matches above, loose matches on Subject: below --
2005-04-27  0:12 Mark Bidewell
2005-04-27  0:13 Mark Bidewell
2005-05-02 14:02 Pallipadi, Venkatesh
2005-05-02 14:30 ` Mark Bidewell

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=426F85F5.7010700@alumni.clemson.edu \
    --to=mark.bidewell@alumni.clemson.edu \
    --cc=cpufreq@lists.linux.org.uk \
    --cc=ivor@ivor.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox