G
Robert Myers said:Regardless of what Myerson thinks, people will be looking at Cell's
~28 gigaflop double precision floating point performance, and
generally not for image processing.
I could point out that the Cell is simply the second iteration of
Sony's PS1 "Emotion Engine", which was predicted when announced to
take over the world. But I won't, because that's irrelevant.
What's relevant is that there is no software to make use of Cell, and
there never will be, except for PS2 games. Thus, the question of
whether there are other architectural deficiencies are irrelevant.
A beast like the Cell is veddy hard to program. Not something to
program in C. Or Cobol. Or Fortran. Or Algol. Hundreds or
thousands of megabytes of assembly code, anyone? ;-)
What's relevant is that there is no software to make use of Cell, and
there never will be, except for PS2 games. Thus, the question of
whether there are other architectural deficiencies are irrelevant.
A beast like the Cell is veddy hard to program. Not something to
program in C. Or Cobol. Or Fortran. Or Algol. Hundreds or
thousands of megabytes of assembly code, anyone? ;-)
from the said:A bird's-eye view, with the bird in geosynchonous orbit, I'm afraid.
Regardless of what Myerson thinks, people will be looking at Cell's
~28 gigaflop double precision floating point performance, and
generally not for image processing.
A bird's-eye view, with the bird in geosynchonous orbit, I'm afraid.
Regardless of what Myerson thinks, people will be looking at Cell's
~28 gigaflop double precision floating point performance, and
generally not for image processing.
I haven't paid much attention
to the details of Cell but outside its intended solution, that kind of FP
performance usually implies huge memory - i.e. is Cell flexible enough to
go there or do you have to do a mod on the basic customized design?
The "Memory capacity problem".
It's addressed in my followup article.
http://www.realworldtech.com/page.cfm?ArticleID=RWT022805234129
Bottomline, IBM didn't want to confirm that the CELL processor will
definitely support up to 72 XDR devices, but it shouldn't be a real
problem. Not to say that the engineering challenges aren't trivial,
but the processor should be able to handle it. It's likely they're
still working on the sub column command support, so they're not
disclosing the x4, x2 and x1 device configuraiton support, even
though the XDR devices support the sub column command modes.
The problem would be to figure out if it's worth it (economics) to
put a bunch of XDR devices on memory modules (saves board space),
and build the memory system that way. (lots of power too)
At it stands, XDR devices are available in 512 Mbit densities,
72 of these suckers gets you 32 GB of ECC (and chipkill too!)
supported memory. That ought to be enough for HPC applications.
Hopefully 1 Gbit XDR devices will arrive on the scene before
someone complains that 32 GB of memory (per processor) isn't
enough.
BTW, I link to Peter Hofstee's paper and presentations given @
HPCA in the reference section. Peter's slides show the Prototype
Sony/IBM CELL rack that's been powered up.