From: Benjamin Herrenschmidt <benh@kernel•crashing.org>
To: Jon Loeliger <jdl@jdl•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:47:24 +1000 [thread overview]
Message-ID: <1151448444.2350.102.camel@localhost.localdomain> (raw)
In-Reply-To: <E1Ftmcb-0007rG-QS@jdl.com>
> > ICTC is such a simple thing to support and you can slow down the CPU
> > pretty comprehensively (from halving to 255x in theory) with an on and
> > off flag. I am surprised nobody implemented a cpufreq governer even if
> > it is totally useless and gives no perceivable benefits..
>
> See? You _are_ contributing already. I encourage
> you to hit the linux-pm@lists•osdl.org list for a spell!
His question is very powerpc specific... I don't see the point of
bringing ICTC related discussions to linux-pm...
Now, we _did_ some experiemnts in the past and didn't see that much
improvements. That might have changed though, since those 744x/745x CPUs
cannot DOZE and we cannot use their NAP mode neither when idle on
Pegasdos, in which case ICTC might have some use there...
It's easy to tweak it, just test and tell us. I'm not sure if cpufreq is
the right interface though as the cpu frequency isn't actually changing.
Ben.
next prev parent reply other threads:[~2006-06-27 22:47 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 [this message]
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=1151448444.2350.102.camel@localhost.localdomain \
--to=benh@kernel$(echo .)crashing.org \
--cc=jdl@jdl$(echo .)com \
--cc=linuxppc-dev@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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