public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: "Matt Sealey" <matt@genesi-usa.com>
To: 'Benjamin Herrenschmidt' <benh@kernel.crashing.org>
Cc: linux-pm@lists.osdl.org
Subject: Re: PowerPC cpufreq using ICTC
Date: Wed, 28 Jun 2006 03:04:06 -0500	[thread overview]
Message-ID: <008101c69a89$6fd20630$99dfdfdf@bakuhatsu.net> (raw)
In-Reply-To: <1151450597.2350.110.camel@localhost.localdomain>

 

> -----Original Message-----
> From: Benjamin Herrenschmidt [mailto:benh@kernel.crashing.org] 
> Sent: Tuesday, June 27, 2006 6:23 PM
> To: matt@genesi-usa.com
> Cc: linux-pm@lists.osdl.org
> Subject: Re: [linux-pm] PowerPC cpufreq using ICTC
> 
> On Tue, 2006-06-27 at 09:56 -0500, Matt Sealey wrote:
> 
> > I'm looking at it from the point of view of the Pegasos 
> > (www.pegasosppc.com) because right now we only have G3 
> (750CXe) and G4 
> > (7447) processor cards which do not support DFS.
> 
> 7447A is supposed to support it no ?

Yeah but we don't ship that processor card (nor a 7448 even
though we have the design and prototypes) and right now.. I
doubt we ever will considering the cost and rather unnoticable
performance improvement in the heavy stuff. Unfortunately there
aren't many customers out there who want do to the kind of
benchmarks you see on the EEMBC scores, the ones that make the
G4 shine, they just want to run MySQL or GNOME..

> >  The G3 is fanless so there is no scope to reduce noise 
> > dynamically or  turn the fan off,
> 
> Also G3 generally support at least DOZE mode when idle, 
> unlike the 7447 where all you have is NAP which is better, 
> but requires proper northbridge support... I would be 
> surprised if the Discovery II used on the Pegasos supports 
> that properly and without funky bugs...

I can find out pretty quickly.. when Gerald gets back in the
office.. *stares at the door*.

> I'm not sure a cpufreq driver is the best thing to do but 
> let's first simply measure if ICTC helps at all... it should 
> be fairly trivial to do a simple kernel module to tweak the value.

One of those links had one (maybe a year old) with a sysfs entry
to mess with. Unfortunately! I don't have the resources to really
test it here without dragging a couple guys away from real important
work. It *DOES* work but I'll be damned if I can see any difference
apart from the speed on the G4, and I don't have a G3 handy to check
the temperature.

-- 
Matt Sealey <matt@genesi-usa.com>
Manager, Genesi, Developer Relations

  reply	other threads:[~2006-06-28  8:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-27 14:56 PowerPC cpufreq using ICTC Matt Sealey
2006-06-27 22:14 ` Guennadi Liakhovetski
2006-06-27 23:23 ` Benjamin Herrenschmidt
2006-06-28  8:04   ` Matt Sealey [this message]
2006-06-29  5:50 ` Paul Mackerras
2006-06-29 12:30   ` Matt Sealey

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='008101c69a89$6fd20630$99dfdfdf@bakuhatsu.net' \
    --to=matt@genesi-usa.com \
    --cc=benh@kernel.crashing.org \
    --cc=linux-pm@lists.osdl.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