From: "Matt Sealey" <matt@genesi-usa.com>
To: <linuxppc-dev@ozlabs.org>
Subject: cpu power "management" for non-dfs chips with no pmu (for instance, 750cxe and mpc7447 in pegasos)
Date: Fri, 23 Jun 2006 05:43:43 -0500 [thread overview]
Message-ID: <018201c696b1$e942ba40$99dfdfdf@bakuhatsu.net> (raw)
Is there any support for using the ICTC to reduce CPU power and so on
for PowerPC currently, in absense of a real PMU like on Macs, or the
dual-PLL/DFS/DFS4 stuff in newer G3 and G4 chips?
I was wondering if there were any definitive performance benchmarks
to see if the setting had any appreciable effect in the first place.
If it doesn't do much more than kill a couple of milliwatts and the
switch between ICTC settings has too high a latency, it would make
no sense in a desktop system.
I am basically trying to evaluate if we can do ANYTHING to reduce
power consumption of systems which are idle, as I have noticed that
for running firmware (sitting at a Forth prompt) and booting a
Linux kernel and doing some work (for instance a simple benchmark),
power consumption barely changes at all. The difference between an
idle G4 and a running G4 is negligible. RC5 makes a big difference
but it is heavily tuned. Most people won't run RC5 all the time to
stress the CPU to the level that it wants to draw a couple extra
watts, I think.
Comments? :)
--
Matt Sealey <matt@genesi-usa.com>
Manager, Genesi, Developer Relations
next reply other threads:[~2006-06-23 10:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-23 10:43 Matt Sealey [this message]
2006-06-23 13:33 ` cpu power "management" for non-dfs chips with no pmu (for instance, 750cxe and mpc7447 in pegasos) Jon Loeliger
2006-06-23 13:58 ` Matt Sealey
2006-06-23 14:26 ` Jon Loeliger
2006-06-23 14:31 ` Matt Sealey
2006-06-23 14:38 ` Raquel Velasco and Bill Buck
2006-06-23 23:49 ` Guennadi Liakhovetski
2006-06-24 16:16 ` Jon Loeliger
2006-06-24 17:29 ` Guennadi Liakhovetski
2006-06-27 22:47 ` Benjamin Herrenschmidt
2006-06-27 22:43 ` Benjamin Herrenschmidt
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='018201c696b1$e942ba40$99dfdfdf@bakuhatsu.net' \
--to=matt@genesi-usa.com \
--cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).