From: Jan Niehusmann <jan@gondor.com>
To: "Grover, Andrew" <andrew.grover@intel.com>
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: VCool - cool your Athlon/Duron during idle
Date: Mon, 27 Aug 2001 11:53:57 +0200 [thread overview]
Message-ID: <20010827115357.A1335@gondor.com> (raw)
In-Reply-To: <4148FEAAD879D311AC5700A0C969E89006CDE0B7@orsmsx35.jf.intel.com>
In-Reply-To: <4148FEAAD879D311AC5700A0C969E89006CDE0B7@orsmsx35.jf.intel.com>
On Mon, Aug 27, 2001 at 02:26:09AM -0700, Grover, Andrew wrote:
> system's ACPI tables indicates they can be used. If you are attempting to
> use C2 even if your system explicitly does not support it, you are asking
> for trouble, just like AMD's errata says.
Motherboard vendors may have disabled the bus disconnection because of a
3% performance hit, to make their boards look better in benchmarks.
In that case, the system may run perfectly stable with disconnection reenabled.
I agree that these experiments should not be performed on a production
system :)
> This results in better battery life on a laptop but that is irrelevant on a
> desktop system.
Well, I think saving ~55W is relevant, even on a desktop system. I plan
to measure how much power these hacks really save, and if it's more than
10W, I think it's worth some more work in this area.
Jan
(asus writes that one of the problems that can happen with this power
saving mode are the huge changes in power dissipation, from 60W to 5W
and back - therefore I assume the power saving mode can save up to 55W)
next prev parent reply other threads:[~2001-08-27 9:54 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-27 9:26 VCool - cool your Athlon/Duron during idle Grover, Andrew
2001-08-27 9:53 ` Jan Niehusmann [this message]
2001-08-27 10:30 ` Slow system with K7 Carlos Costa Portela
2001-08-27 10:46 ` Alan Cox
2001-08-27 11:48 ` VCool - cool your Athlon/Duron during idle Liakakis Kostas
2001-08-27 15:03 ` Kurt Roeckx
2001-08-27 18:23 ` Liakakis Kostas
2001-08-27 20:56 ` Paul G. Allen
2001-08-27 10:42 ` Alan Cox
2001-08-27 12:16 ` Dieter Nützel
2001-08-27 20:17 ` Paul G. Allen
2001-09-02 22:28 ` Jan Niehusmann
-- strict thread matches above, loose matches on Subject: below --
2001-08-27 20:57 Grover, Andrew
[not found] <87pu9i7frm.fsf@psyche.kn-bremen.de.suse.lists.linux.kernel>
[not found] ` <E15b6Rz-0002hM-00@the-village.bc.nu.suse.lists.linux.kernel>
2001-08-27 6:55 ` Andi Kleen
[not found] <87pu9i7frm.fsf@psyche.kn-bremen.de>
2001-08-26 20:24 ` Alan Cox
2001-08-26 18:09 Dieter Nützel
2001-08-26 19:24 ` Alan Cox
2001-08-26 20:00 ` Lehmann
2001-08-26 22:40 ` Andreas Bombe
2001-08-26 20:25 ` Dieter Nützel
2001-08-26 23:00 ` Jan Niehusmann
2001-08-27 22:46 ` Pavel Machek
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=20010827115357.A1335@gondor.com \
--to=jan@gondor.com \
--cc=andrew.grover@intel.com \
--cc=linux-kernel@vger.kernel.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