All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Krafft <krafft@de.ibm.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: parabelboi@bopserverein.de, cpufreq@lists.linux.org.uk,
	cbe-oss-dev@ozlabs.org
Subject: Re: [Cbe-oss-dev] [Patch] Resending: cell_add_spuaware_cpufreq_governor.diff
Date: Wed, 16 Apr 2008 16:53:07 +0200	[thread overview]
Message-ID: <20080416165307.1d7a4258@de.ibm.com> (raw)
In-Reply-To: <200804161408.26145.arnd@arndb.de>


[-- Attachment #1.1: Type: text/plain, Size: 1522 bytes --]

On Wed, 16 Apr 2008 14:08:25 +0200
Arnd Bergmann <arnd@arndb.de> wrote:

> On Wednesday 16 April 2008, Christian Krafft wrote:
> > This patch is also missing a correct load calculation.
> > It works pretty well for spu's running at full time or idling, but not so
> > well for mixed load (i.e. each spu running 50 percent of the time we would
> > switch to fullspeed instead of half speed).
> 
> So why should that be something to optimize for? If the SPUs are all idle,
> I would assume we'd be better off throwing the tasks off and putting them
> into low-power mode, rather than changing the frequency, right?
> 
> What's the point of your driver, really?
> 
> 	Arnd <><

What we have now is good enough to
- switch to full power if there are spus active (waiting or running) and 
- switch to low power if not.

What we have now is not good enough to
- switch to low power if there are spus waiting, but none are running

As we cannot _yet_ differentiate between spus waiting and spus running means
that in _some_ cases we will not save as much power as we could.

The point of submitting the driver is to get it working.
Further improvements will follow of course.

-- 
Mit freundlichen Gruessen,
kind regards,

Christian Krafft
IBM Systems & Technology Group,
Linux Kernel Development
IT Specialist


Vorsitzender des Aufsichtsrats:	Martin Jetter
Geschaeftsfuehrung:		Herbert Kircher
Sitz der Gesellschaft:		Boeblingen
Registriergericht:		Amtsgericht Stuttgart, HRB 243294

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 147 bytes --]

_______________________________________________
Cpufreq mailing list
Cpufreq@lists.linux.org.uk
http://lists.linux.org.uk/mailman/listinfo/cpufreq

  reply	other threads:[~2008-04-16 14:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-18 16:11 Subject: cell: add spu aware cpufreq governor Christian Krafft
2008-01-19 21:38 ` [Cbe-oss-dev] " Arnd Bergmann
2008-01-28 18:03   ` Christian Krafft
2008-01-28 18:12     ` [Cbe-oss-dev] [Patch] Resending: " Christian Krafft
2008-04-14  0:21       ` Arnd Bergmann
2008-04-16 11:49         ` [Cbe-oss-dev] [Patch] Resending: cell_add_spuaware_cpufreq_governor.diff Christian Krafft
2008-04-16 12:08           ` Arnd Bergmann
2008-04-16 14:53             ` Christian Krafft [this message]
2008-01-21  3:09 ` [Cbe-oss-dev] Subject: cell: add spu aware cpufreq governor Akinobu Mita
2008-01-28 10:26   ` Christian Krafft

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=20080416165307.1d7a4258@de.ibm.com \
    --to=krafft@de.ibm.com \
    --cc=arnd@arndb.de \
    --cc=cbe-oss-dev@ozlabs.org \
    --cc=cpufreq@lists.linux.org.uk \
    --cc=parabelboi@bopserverein.de \
    /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.