From: bert hubert <bert.hubert@netherlabs.nl>
To: Robert Hancock <hancockr@shaw.ca>
Cc: David Rees <drees76@gmail.com>,
Arjan van de Ven <arjan@infradead.org>,
Tomasz Torcz <zdzichu@irc.pl>,
linux-kernel@vger.kernel.org, zwane@arm.linux.org.uk
Subject: Re: 2.6.18 regression: cpufreq broken since 2.6.18-rc1 on pentium4
Date: Mon, 31 Jul 2006 21:35:07 +0200 [thread overview]
Message-ID: <20060731193507.GC16797@outpost.ds9a.nl> (raw)
In-Reply-To: <44CE567D.40305@shaw.ca>
On Mon, Jul 31, 2006 at 01:14:05PM -0600, Robert Hancock wrote:
> per watt. As well, when the CPU has nothing to do it will be halted
> anyway which does pretty much the same as what clockmod is doing.
You are empirically wrong in my case. I can't make you hear the difference
in noise, but perhaps this will convince you:
$ sensors | grep CPU
CPU_Fan: 2359 RPM (min = 4000 RPM)
CPU: +61 C (low = +10 C, high = +50 C)
$ sudo /etc/init.d/powernowd start
* Starting powernowd... [ ok ]
$ sensors | grep CPU
CPU_Fan: 1411 RPM (min = 4000 RPM)
CPU: +57 C (low = +10 C, high = +50 C)
$ sudo /etc/init.d/powernowd stop
* Stopping powernowd: [ ok ]
$ sensors | grep CPU
CPU_Fan: 2452 RPM (min = 4000 RPM)
CPU: +61 C (low = +10 C, high = +50 C)
And this with only seconds in between starting and stopping, on an idle
system.
> Essentially clockmod is there as a way to limit the thermal output of
> the CPU in thermal emergencies, it's not really very good as a
> power-saving feature.
That I've measured, and indeed, the same amount of power is drawn from the
mains. But the reduction in fan noise is worth it.
On this CPU, HLT may simply not be doing as good a job. Who knows.
processor : 0
vendor_id : GenuineIntel
cpu family : 15
model : 4
model name : Intel(R) Pentium(R) 4 CPU 3.00GHz
stepping : 1
cpu MHz : 3000.000
cache size : 1024 KB
It does reduce effective CPU to 300MHz though, which is a lot.
Kind regards,
bert
--
http://www.PowerDNS.com Open source, database driven DNS Software
http://netherlabs.nl Open and Closed source services
next prev parent reply other threads:[~2006-07-31 19:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.I17h4UhBWCsvus2I0Myp7dcrW/c@ifi.uio.no>
[not found] ` <fa.+Nle/k4hS56BZtGd2LF1VOaLvRg@ifi.uio.no>
2006-07-31 19:14 ` 2.6.18 regression: cpufreq broken since 2.6.18-rc1 on pentium4 Robert Hancock
2006-07-31 19:35 ` bert hubert [this message]
2006-07-30 12:08 bert hubert
2006-07-30 16:07 ` Tomasz Torcz
2006-07-30 17:45 ` Zwane Mwaikambo
2006-07-31 5:56 ` Tomasz Torcz
2006-07-31 14:04 ` Zwane Mwaikambo
2006-07-31 15:22 ` Tomasz Torcz
2006-07-30 19:46 ` Arjan van de Ven
2006-07-30 19:53 ` bert hubert
2006-07-31 7:50 ` David Rees
2006-07-31 8:12 ` bert hubert
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=20060731193507.GC16797@outpost.ds9a.nl \
--to=bert.hubert@netherlabs.nl \
--cc=arjan@infradead.org \
--cc=drees76@gmail.com \
--cc=hancockr@shaw.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=zdzichu@irc.pl \
--cc=zwane@arm.linux.org.uk \
/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