From: Dennis Schridde <devurandom@gmx.net>
To: Michael Ellerman <michael@ellerman.id.au>
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 13:51:55 +0200 [thread overview]
Message-ID: <20130423135155.7b307094@samson> (raw)
In-Reply-To: <20130423091246.GA18195@concordia>
[-- Attachment #1: Type: text/plain, Size: 1011 bytes --]
Hello Michael!
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.
> Does your cellminer actually work? ie. does it run OK?
>
> I am using a fractal benchmark I had lying around, and it appears to
> work, and runs fast enough that it must be running on the SPUs (I
> think).
>
> So it sounds like we have some weirdness with stuff not appearing in
> /spu, but spu programs are still able to run. Which is odd to say the
> least.
Yes, that seems to be exactly what I see here. The SPE code seems to be
actually running (cellminer reports SPU threads being created and it
runs at 42 Megahash/s - which is coming closer and closer to the
expected ~60Mh/s, given that I started with about 6Mh/s), just /spu is
empty.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2013-04-23 11:52 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 [this message]
2013-04-23 13:16 ` Dennis Schridde
2013-04-23 13:19 ` Michael Ellerman
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=20130423135155.7b307094@samson \
--to=devurandom@gmx.net \
--cc=arnd@arndb.de \
--cc=cbe-oss-dev@lists.ozlabs.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=michael@ellerman.id.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.