From: "Paul G. Allen" <pgallen@randomlogic.com>
To: unlisted-recipients:; (no To-header on input)@localhost.localdomain
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>,
"kplug-list@kernel-panic.org" <kplug-list@kernel-panic.org>
Subject: Re: VCool - cool your Athlon/Duron during idle
Date: Mon, 27 Aug 2001 13:56:59 -0700 [thread overview]
Message-ID: <3B8AB41B.3B75F4B9@randomlogic.com> (raw)
In-Reply-To: <Pine.GSO.4.21.0108272108430.14459-100000@skiathos.physics.auth.gr>
Liakakis Kostas wrote:
>
> On Mon, 27 Aug 2001, Kurt Roeckx wrote:
>
> > On Mon, Aug 27, 2001 at 02:48:24PM +0300, Liakakis Kostas wrote:
> > > On Mon, 27 Aug 2001, Jan Niehusmann wrote:
> > >
> > > > (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)
> > >
> > > The problem they are describing is not the change in power dissipation,
> > > but the change in current draw from the regulated 1.75V (difference of
> > > about 30A or more).
> >
> > And what do you think power is?
> > Maybe it's the voltage times the current?
>
> Your point being? This is power yeah. However I can get 50W with 1V@50A
> and with 50V@1A ... tell me which will be easier for a regulator when
> going from 10 to 50W while trying to keep the voltage steady.
First of all, let me say that I used to run the lab at NCR Corporation testing and qualifying power supplies, and making design recommendations/changes when
they failed, for main frame computers.
That would depend upon the power supply, and specifically, the regulator design. Consider that the average PC user buys a cheap $30 - $50 (US Dollars) case and
P/S package. That P/S will never be able to handle this kind of transition and stay within its specified regulation. In the electronics industry, you get what
you pay for (with the exception of a couple of big names that simply sell junk 'cause they can), and there's no exception to this rule when it comes to power
supplies. I have tested PC power supplies by various mfgs. and have found that most do not hold up to the specifications printed on them, let alone to anything
a CPU/MB mfg. may require. Many operate on the fringe of their specified voltage range even under low load, send them up to maximum load and they quickly fly
south (and many never return!). In simple terms, you won't find a P/S under $100 (US) that will be worth the CPUs weight in regulation, let alone will be able
to handle such a large power transition.
>
> So to rephrase myself the condition of less power dissipation (and that is
> thermal output, not power consumption which isvoltage times current... )
> is the result of less current draw of ~30A. This is a huge difference. And
> this is the problem. There are regulators on certain motherboards which
> can't cope with this. And they increase (not that bad unless you fry a
> chip) when current drops, or decrease voltage when there is current need
> (crash) of the tolerance limmits.
MoBo regulators aside, as stated above, most power supplies can't handle it, so there's nothing the regulator could do no matter how well designed it is. What I
said above does stand for on-board regulators as well.
BTW, there are two basic power ratings for an electronic component - Power Dissipation (Pd) and Power Consumption (Pc). Pd is the amount of power (V*I or
Voltage times Current) that the component wastes in heat (which is generated by the friction of electrons moving through the component). Pc is the total power
required by the component for operation, and is a function of Pd plus the power actually used by the component and not wasted in heat. Pc is also V*I. Pc is
measured by connecting meters (voltage and current) to the power connections on the component while in operation. Pd can be measured by the amount of heat
coming off of it, or by various other methods. Both Pd and Pc can be decreased by turning off portions of the component, decreasing clock speed (thereby
decreasing friction), and by decreasing voltage and/or current to minimum operational levels. It can be increased by turning off the wrong portions of the
component causing others to exceed their specifications, by increasing clock speed, by increasing voltage and/or current to maximum operational levels (or
beyond - a Bad Thing :), and by decreasing voltage and/or current below operational levels. The last scenario causes the component to do all kinds of things it
wasn't meant to do, which usually causes Pd to rise dramatically and therefore Pc follows.
So, in summary, I wouldn't use power saving modes (and I don't) unless:
1. I had 100% conviction that my P/S would meet or exceed the required specifications.
2. I had 100% conviction that the MoBo would meet or exceed the required specifications.
3. I had 100% conviction that all components in the system would meet or exceed the required specifications.
More often that not, they don't, and most consumers are none the wiser. I have never used any power saving mode because in any given case the system in question
could not meet 1 - 3.
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:50 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 [this message]
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=3B8AB41B.3B75F4B9@randomlogic.com \
--to=pgallen@randomlogic.com \
--cc=kplug-list@kernel-panic.org \
--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