5 ms·
"The Race for a New Game Machine"[1] is a pretty good read on the development of the Cell and Xenon[2] processors. Giving up the out-of-order seems like a real
by protomyth 11y ago
"The Race for a New Game Machine"[1] is a pretty good read on the development of the Cell and Xenon[2] processors. Giving up the out-of-order seems like a really bad decision and the internal fighting at IBM, if accurate, is really sad.
A side question: What in the POWER architecture makes it hard to implement? I was told the addressing modes are complicated enough that it will always be slower and harder to create than other processors. I'm wondering if this is urban myth or has some basis in reality?
1) http://www.amazon.com/The-Race-New-Game-Machine/dp/0806531010 http://www.amazon.com/The-Race-New-Game-Machine/dp/080653101... with a lot of articles written about the book such as http://www.wsj.com/articles/SB123069467545545011 http://www.wsj.com/articles/SB123069467545545011
2) https://en.wikipedia.org/wiki/Xenon_(processor) https://en.wikipedia.org/wiki/Xenon_(processor)
- russellbeattie 11y agoI really enjoyed this book - it wasn't on the level of "Soul of a New Machine" in terms of writing, but the subject matter was really interesting. As a software guy, it was a great way to understand what's going on at the lowest level of computing. Not from an in-depth technical level, but from a "what do chip designers actually do??" perspective. You know, after they sit down at their desks, what is the work involved? Also, the insight into how corporations have to make hardware decisions years before really came through as well - the book starts in 2000 if I remember correctly. I'd love to see a follow-on book about how AMD landed both the PS4 and XBox One.
- trsohmers 11y agoIt wasn't due to the POWER architecture, it was the SPEs, which were not based on POWER. The biggest problem for compilers and developers of the day was the fact that each of the SPE cores had their own local memory ("scratchpad") that is similar to a cache, but is not hardware managed. My company (REX Computing) is working on a new processor architecture that is built around scratchpad memory... the main benefits of a scratchpad are that it is lower latency (which basically means faster), uses less area and power, and can be built into larger arrays than your regular hardware managed caches. The big drawback, as seen by Cell, is the fact that it is difficult for most programmers to manually manage their memory. Our big advancement is that we've developed new compiler techniques (which have been DARPA funded), that would not only make it a lot easier to program the Cell architecture, but allows us to go even further than they did with Cell in making a highly parallelized and energy efficient processor.
- scott_s 11y agoI'm very interested in reading any public information you have on this work.
- trsohmers 11y agoWould love to share more info, but I should have stated that it won't magically make Cell simple to program for... our new compiler techniques are dependent on a lot of new architectural ideas we have implemented in hardware, and while we would solve the memory cramming problem (Trying to fit your application into the fixed scratchpad space) on many architectures (Cell, TI DSPs, a lot of other embedded chips), the real magic we have developed is in being able to have 90%+ of it statically scheduled, which we're only able to do with our architecture. If you're interested, check out our website (http://rexcomputing.com http://rexcomputing.com) and sign up for the mailing list... The only thing we have public is a very vague and more technique overview paper in general rather than a real description of what we are doing(http://memsys.io/wp-content/uploads/2015/09/p98-sebexen.pdf http://memsys.io/wp-content/uploads/2015/09/p98-sebexen.pdf). It presented at a conference earlier this month (and to be published by the ACM), but I hope to give more details on our specific implementation and other cool features later this year. If you're willing to sign a NDA, feel free to use the contact us on the website though.
- protomyth 11y agoActually, I wasn't referring to the SPEs, I specifically heard the POWER architecture had some stuff that made it hard to implement and slower than other RISCs.
- cbsmith 11y agoAs was aptly demonstrated by x86 systems (both now and in that era), transistor budgets had grown enough by the time Cell came of age that the impact of ISAs could have on overall performance was comparatively trivial. POWER had a lot of funny things about it, but it wasn't that hard to get POWER architectures to move quickly.