From: Ducrot Bruno <ducrot@poupinou.org>
To: Wouter Verhelst <wouter@grep.be>, cpufreq@www.linux.org.uk
Subject: Re: p4-clockmod doesn't seem to allow the highest possible speed
Date: Sun, 11 Jan 2004 19:05:59 +0100 [thread overview]
Message-ID: <20040111180559.GD14031@poupinou.org> (raw)
In-Reply-To: <20040111173003.GA5485@dominikbrodowski.de>
On Sun, Jan 11, 2004 at 06:30:03PM +0100, Dominik Brodowski wrote:
> On Sun, Jan 11, 2004 at 04:48:25PM +0100, Ducrot Bruno wrote:
> > (but that do
> > not matter, since you should use p4-clockmod instead of ACPI T-states
> > anyway).
>
> What are the advantages of p4-clockmod in favour of ACPI T-states?
>
1- Latency (MSR access instead of ISA IO space).
2- Safety (p4-clockmod do not rely on external circuitry, or hw bugs from
the southbridge).
3- even though I don't think p4-clockmod do not support this, it is
possible to throttle the CPU in case of overheating issue, without
need to do that in software.
4- a little more power efficient, since generating a signal cost power
(but I don't think that you gain so much).
--
Ducrot Bruno
-- Which is worse: ignorance or apathy?
-- Don't know. Don't care.
next prev parent reply other threads:[~2004-01-11 18:05 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-09 18:18 p4-clockmod doesn't seem to allow the highest possible speed Wouter Verhelst
2004-01-10 10:15 ` Dominik Brodowski
2004-01-10 11:08 ` Wouter Verhelst
2004-01-10 13:18 ` Dominik Brodowski
2004-01-10 15:02 ` Wouter Verhelst
2004-01-10 15:38 ` Dominik Brodowski
2004-01-10 16:30 ` Wouter Verhelst
2004-01-10 15:21 ` Wouter Verhelst
2004-01-10 15:41 ` Dominik Brodowski
2004-01-10 16:32 ` Wouter Verhelst
2004-01-10 18:53 ` Ducrot Bruno
2004-01-10 19:35 ` Wouter Verhelst
2004-01-11 15:48 ` Ducrot Bruno
2004-01-11 17:30 ` Dominik Brodowski
2004-01-11 18:05 ` Ducrot Bruno [this message]
2004-01-11 17:35 ` Dominik Brodowski
2004-01-11 19:56 ` Wouter Verhelst
2004-01-11 20:06 ` Dominik Brodowski
2004-01-11 20:24 ` Wouter Verhelst
2004-01-12 12:26 ` Ducrot Bruno
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=20040111180559.GD14031@poupinou.org \
--to=ducrot@poupinou.org \
--cc=cpufreq@www.linux.org.uk \
--cc=wouter@grep.be \
/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.