linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: matt@genesi-usa.com
Cc: linuxppc-dev@ozlabs.org
Subject: Re: cpu power "management" for non-dfs chips with no pmu (for instance, 750cxe and mpc7447 in pegasos)
Date: Wed, 28 Jun 2006 08:43:57 +1000	[thread overview]
Message-ID: <1151448237.2350.98.camel@localhost.localdomain> (raw)
In-Reply-To: <018201c696b1$e942ba40$99dfdfdf@bakuhatsu.net>


> 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.

Well, I would expect the Idle G4 to have a fairly good PM in the first
place due to the NAP mode... though we may not enable that on Pegasos.
It depends if the bridge supports the proper protocol to handle
snooping. The Discovery II is bad enough as it is, I wouldn't expect it
to support that in a non-buggy way unfortunately.

Ben.

      parent reply	other threads:[~2006-06-27 22:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-23 10:43 cpu power "management" for non-dfs chips with no pmu (for instance, 750cxe and mpc7447 in pegasos) Matt Sealey
2006-06-23 13:33 ` 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 [this message]

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=1151448237.2350.98.camel@localhost.localdomain \
    --to=benh@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=matt@genesi-usa.com \
    /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).