From: "Paul G. Allen" <pgallen@randomlogic.com>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: VCool - cool your Athlon/Duron during idle
Date: Mon, 27 Aug 2001 13:17:10 -0700 [thread overview]
Message-ID: <3B8AAAC6.6330014E@randomlogic.com> (raw)
In-Reply-To: <E15bJr2-0003fx-00@the-village.bc.nu>
Alan Cox wrote:
>
> > handle a too-hot cpu, but all C2/C3 gets you is reduced power when =
> > idle.
> > This results in better battery life on a laptop but that is irrelevant =
> > on a
> > desktop system.
>
> Thus speaks the country with chronic californian power shortages, and that
> wouldn't sign up to a global accord on global warming 8)
>
In reality, California has no power shortage. The problem is deregulation and greed together causing an artificial power shortage. Tell those of us in San Diego
that we're using too much power and there's a shortage. We started conserving a year before the "shortage" - an average of 20% in fact - and we still had
blackouts and higher rates and were told to cut back even more or pay even more. But, this thread digresses.
> C2 and C3 are useful IMHO even on a desktop PC. The slight hit on the
> transition is not noticable, the change on the power bill is.
At our rates, you're darn right it is. An average PC costs ~$.05 per hour to run in California.
PGA
--
Paul G. Allen
UNIX Admin II/Programmer
Akamai Technologies, Inc.
www.akamai.com
Work: (858)909-3630
Cell: (858)395-5043
next prev parent reply other threads:[~2001-08-27 20:10 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
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 [this message]
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=3B8AAAC6.6330014E@randomlogic.com \
--to=pgallen@randomlogic.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