All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bas Mevissen <ml@basmevissen.nl>
To: Norbert Preining <preining@logic.at>
Cc: cpufreq@www.linux.org.uk
Subject: Re: Which cpufreq driver is best for ...
Date: Wed, 03 Sep 2003 13:37:05 +0200	[thread overview]
Message-ID: <3F55D261.6010407@basmevissen.nl> (raw)
In-Reply-To: <20030903055749.GA21721@gamma.logic.tuwien.ac.at>

Norbert Preining wrote:

> Hi!
> 
> Which cpufreq driver is best for 
> 	Mobile Intel(R) Pentium(R) 4 - M CPU 2.20GHz
> I can use the
> 	p4-clockmod
> and the
> 	speedstep-ich
> With the p4-clockmod I can adapt the freq between 274MHz and 2.2GHz,
> while with speedstep-ich I can only go between 1.2GHz and 2.2GHz. So I
> guess p4-clockmod is superior for my chip/cpu.
> 

It depends on what you want. If you want to get battery life to the max 
(and power consumption/heat production as low as possible), you need 
p4-clockmod.

I just use speedstep-ich on mu P4@2.0G (Dell Inspiron 8500) only to 
switch between 1.2GHz and 2.0GHz. My main use is lowering the 
temperature and rising the battery life when I'm working with my labtop 
litterly as lab-top (and no longer getting heated up too much by the 
notebook :-) ).

So I'm happy with the "heat control" only, you might want to have more 
than that.

> In the same line - are there any new governors with `intelligent'
> scaling techniques. ATM I am using cpudyn, which switches between min
> and max frequences.
> 

If you use speedstep-ich, you might only want to switch speeds depending 
on AC or battery power, eventually with manual override. That should be 
possible with e.g. acpid and some scripts, while using cpufreq in 
userspace governer mode.

If you really want the best battery life, you can use/write a governor 
that depends on e.g. load. (I've seen something about that somewhere.)

Regards,

Bas.

  reply	other threads:[~2003-09-03 11:37 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-03  5:57 Which cpufreq driver is best for Norbert Preining
2003-09-03 11:37 ` Bas Mevissen [this message]
2003-09-03 14:32   ` Norbert Preining
2003-09-03 15:52     ` Mattia Dongili
2003-09-03 19:30   ` Dominik Brodowski
2003-09-03 19:50     ` Norbert Preining
2003-09-03 21:01       ` Dominik Brodowski
2003-09-04  7:09         ` Norbert Preining
2003-09-04  9:46           ` Dominik Brodowski
2003-09-04  9:59             ` Norbert Preining
2003-09-04 10:04               ` Dominik Brodowski
2003-09-04  9:57         ` Norbert Preining
2003-09-07 19:12           ` Dominik Brodowski
2003-09-04 12:25     ` Bas Mevissen
2003-09-03 19:27 ` Dominik Brodowski
2003-09-04 12:36   ` Bas Mevissen
2003-09-04 23:27     ` Dominik Brodowski
2003-09-05  8:15       ` Bas Mevissen

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=3F55D261.6010407@basmevissen.nl \
    --to=ml@basmevissen.nl \
    --cc=cpufreq@www.linux.org.uk \
    --cc=preining@logic.at \
    /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.