From: Eric Blossom <eb@comsec.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Dave Jones <davej@codemonkey.org.uk>,
Stephen Rothwell <sfr@canb.auug.org.au>,
cpufreq@lists.linux.org.uk, linuxppc-dev@ozlabs.org,
Jeremy Kerr <jk@ozlabs.org>,
cbe-oss-dev@ozlabs.org
Subject: Re: [Cbe-oss-dev] powerpc/cell/cpufreq: add spu aware cpufreq governor
Date: Mon, 7 Jul 2008 10:17:32 -0700 [thread overview]
Message-ID: <20080707171732.GC26603@comsec.com> (raw)
In-Reply-To: <200807071702.31240.arnd@arndb.de>
On Mon, Jul 07, 2008 at 05:02:30PM +0200, Arnd Bergmann wrote:
> From: Christian Krafft <krafft@de.ibm.com>
>
> This patch adds a cpufreq governor that takes the number of running spus
> into account. It's very similar to the ondemand governor, but not as complex.
> Instead of hacking spu load into the ondemand governor it might be easier to
> have cpufreq accepting multiple governors per cpu in future.
> Don't know if this is the right way, but it would keep the governors simple.
I've got a basic question about this idea:
Does it throttle only idle spus or is there a single control for
the entire PPE + SPE complex?
I can think of many situations in our code where at certain times we
may only be able to keep N out of M spes occupied (because of how
we've expressed our task-specific parallelism), but we're counting on
the ones we're using running at full speed so that we can maintain our
real-time throughput. (Our application does real-time signal
processing of continuously streaming data)
Is there a way to disable the "throttling SPEs" feature short of
configuring it out of the kernel?
Eric
next prev parent reply other threads:[~2008-07-07 17:17 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-07 15:02 powerpc/cell/cpufreq: add spu aware cpufreq governor Arnd Bergmann
2008-07-07 15:02 ` Arnd Bergmann
2008-07-07 17:17 ` Eric Blossom [this message]
2008-07-07 21:02 ` [Cbe-oss-dev] " Arnd Bergmann
2008-07-07 21:02 ` Arnd Bergmann
2008-07-07 21:31 ` Dave Jones
2008-07-07 21:31 ` Dave Jones
2008-07-08 6:43 ` Arnd Bergmann
2008-07-08 6:43 ` Arnd Bergmann
2008-07-08 15:27 ` Dave Jones
2008-07-08 15:27 ` Dave Jones
2008-07-09 3:41 ` Benjamin Herrenschmidt
2008-07-09 3:57 ` Dave Jones
2008-07-10 18:05 ` Dominik Brodowski
2008-07-10 18:05 ` Dominik Brodowski
2008-07-10 21:05 ` Arnd Bergmann
2008-07-10 21:16 ` Dominik Brodowski
2008-07-09 5:18 ` Benjamin Herrenschmidt
2008-07-09 6:29 ` Dave Jones
2008-07-15 13:02 ` Arnd Bergmann
2008-07-15 13:02 ` Arnd Bergmann
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=20080707171732.GC26603@comsec.com \
--to=eb@comsec.com \
--cc=arnd@arndb.de \
--cc=cbe-oss-dev@ozlabs.org \
--cc=cpufreq@lists.linux.org.uk \
--cc=davej@codemonkey.org.uk \
--cc=jk@ozlabs.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=sfr@canb.auug.org.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.