cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Dominik Brodowski <linux@dominikbrodowski.de>
Cc: Bruno Ducrot <ducrot@poupinou.org>,
	holbling@cpt.univ-mrs.fr, cpufreq@www.linux.org.uk
Subject: Re: [PATCH] 2.6.5 speedstep on P4Ms
Date: Wed, 09 Jun 2004 17:29:00 +0100	[thread overview]
Message-ID: <1086798540.31338.6.camel@delerium.codemonkey.org.uk> (raw)
In-Reply-To: <20040609154710.GA9482@dominikbrodowski.de>

On Wed, 2004-06-09 at 16:47, Dominik Brodowski wrote:
> Hi Chris,
> 
> > for 3): what you say sounds much better than my brutal hack, so i won't 
> > post it again. i'd definitely want to try to implement 2 cpufreq 
> > drivers, but i fear this is way beyond me at the moment and probably 
> > involves design choices i can't make.
> 
> well, somebody _does_ have to do design choices... However, I'm not yet
> convinced of the necessity of supporting throttling and frequency scaling on
> the same system. Even more, under normal circumstances [i.e. idling works,
> which it does on most systems], I see no _technical_ reason to do
> throttling, or even non-temperature related _dynamic throttling_ like other
> OSes do it. For those new to this list, there's some maths in the archives
> which proves that you need more energy == battery power if you do
> throttling for any given task... So it's something we need to discuss 
> during 2.7.

I'm actually inclined to kill off p4-clockmod one day.
It doesn't seem to do anything useful whatsoever.
It certainly doesn't lower the temperature on my xeon.

	Dave

  parent reply	other threads:[~2004-06-09 16:29 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-08 17:15 [PATCH] 2.6.5 speedstep on P4Ms Christian Hoelbling
2004-06-08 15:30 ` Bruno Ducrot
2004-06-08 23:53   ` Christian Hoelbling
2004-06-09 15:47     ` Dominik Brodowski
2004-06-09 16:09       ` Bruno Ducrot
2004-06-09 16:29       ` Dave Jones [this message]
2004-06-09 16:53         ` Dominik Brodowski
2004-06-09 18:32           ` Mattia Dongili
2004-06-10  0:46       ` Christian Hoelbling
2004-06-10  8:30         ` Dominik Brodowski
2004-06-10 11:20           ` Dave Jones
2004-06-10  9:10         ` Bruno Ducrot
2004-06-10 15:37         ` Bruno Ducrot
2004-06-10 16:44           ` Dominik Brodowski
2004-06-10 19:26             ` [PATCH] Remove notify in speedstep_set_state [1/2] Bruno Ducrot
2004-06-10 19:28             ` [PATCH] Remove notify in speedstep_set_state [2/2] Bruno Ducrot
2004-06-10 19:35             ` [PATCH] security fix for speedstep-smi Bruno Ducrot
2004-06-10 19:44             ` [PATCH] 2.6.5 speedstep on P4Ms Bruno Ducrot
2004-06-10 20:04             ` [PATCH] replace for_each_cpu with for_each_cpu_mask (was Re: [PATCH] 2.6.5 speedstep on P4Ms) Bruno Ducrot
2004-06-10 21:38               ` Dave Jones
2004-06-11  9:55                 ` Bruno Ducrot
  -- strict thread matches above, loose matches on Subject: below --
2004-06-11  0:21 [PATCH] 2.6.5 speedstep on P4Ms Christian Hoelbling
2004-06-11  0:30 Christian Hoelbling

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=1086798540.31338.6.camel@delerium.codemonkey.org.uk \
    --to=davej@redhat.com \
    --cc=cpufreq@www.linux.org.uk \
    --cc=ducrot@poupinou.org \
    --cc=holbling@cpt.univ-mrs.fr \
    --cc=linux@dominikbrodowski.de \
    /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