From: Michael Ellerman <michael@ellerman.id.au>
To: Dennis Schridde <devurandom@gmx.net>
Cc: cbe-oss-dev@lists.ozlabs.org, linuxppc-dev@lists.ozlabs.org,
arnd@arndb.de
Subject: Re: PROBLEM: Only 2 of 4 cores used on IBM Cell blades and no threads shown in spufs
Date: Tue, 23 Apr 2013 23:19:11 +1000 [thread overview]
Message-ID: <20130423131911.GA1078@concordia> (raw)
In-Reply-To: <3242341.cjDFP0lvB2@ernie>
On Tue, Apr 23, 2013 at 03:16:53PM +0200, Dennis Schridde wrote:
> Hello!
>
> Am Dienstag, 23. April 2013, 13:51:55 schrieb Dennis Schridde:
> > Am Tue, 23 Apr 2013 19:12:47 +1000
> > schrieb Michael Ellerman <michael@ellerman.id.au>:
> > > On Mon, Apr 22, 2013 at 06:44:13PM +0200, Dennis Schridde wrote:
> > > For me it is fixed by applying the following patch, it should be in
> > > v3.10:
> > I am currently compiling the patched kernel. Will report back with the
> > results later.
>
> Thanks! The patch has the intended result on my Linux 3.8.8 kernel. All 4 CPU
> cores are now being used and the cellminer hashrate went up from 42Mh/s to
> 62Mh/s (with 2 PPE and 16 SPE threads, just as before).
Excellent.
> Could it be backported, especially to 3.8?
Yes we'll send it to stable.
cheers
next prev parent reply other threads:[~2013-04-23 13:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-22 16:44 PROBLEM: Only 2 of 4 cores used on IBM Cell blades and no threads shown in spufs Dennis Schridde
2013-04-23 9:12 ` Michael Ellerman
2013-04-23 11:51 ` Dennis Schridde
2013-04-23 13:16 ` Dennis Schridde
2013-04-23 13:19 ` Michael Ellerman [this message]
2013-05-17 15:46 ` Dennis Schridde
2013-05-22 3:37 ` Michael Ellerman
2013-04-23 12:01 ` Dennis Schridde
2013-04-23 12:16 ` Michael Ellerman
2013-04-23 12:41 ` Dennis Schridde
2013-04-23 12:53 ` Michael Ellerman
2013-04-23 13:24 ` Michael Ellerman
2013-04-23 18:13 ` Dennis Schridde
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=20130423131911.GA1078@concordia \
--to=michael@ellerman.id.au \
--cc=arnd@arndb.de \
--cc=cbe-oss-dev@lists.ozlabs.org \
--cc=devurandom@gmx.net \
--cc=linuxppc-dev@lists.ozlabs.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 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.