Those of you interested in the IBM chip that will power the Nintendo Revolution, called Broadway, may be interested in following this thread while you wait for the article to be published at a later date.
They'd possibly want to do it because Nintendo is a very ease-of-development-centric company these days, as opposed to highest peak performance figures. The Cube was universally recognized as a very forgiving platform, ie, it ran relatively well even if you did deliberately stupid things with it, and everything Nintendo has said about Rev speaks for the same being true for it as well, probably even more so in fact. GC had the biggest caches (by far) last time 'round, it would seem logical they'll follow a similar philosophy this time 'round.pc999 said:why would they want to put 2MB of L2 cache?, ie considering what the others are doing unless they really want t make it very easy devolopment, but it seems that it would be a wast of "performance" or money, IMO.
Teasy said:I was looking at the power consumption of the 970FX earlier and noticed how it drops off very fast with only a small speed drop. For instance at its fastest speed of 2.2Ghz the CPU consumes 48 watts and at 2Ghz it consumes 40 watts. Yet at 1.6Ghz it consumes only 17 watts! That's a 57.5% drop in power consumption based on only a 20% downclock. Could the XCPU in 360 act similarly? Assuming 3.2Ghz is the cutting edge speed for the CPU (which seems very likely) and the CPU consumes 85W at that speed. Could that mean that a 2.6Ghz version might consume less then half that (under 40W)? Not making any claims, just asking a question.
Teasy said:I was looking at the power consumption of the 970FX earlier and noticed how it drops off very fast with only a small speed drop. For instance at its fastest speed of 2.2Ghz the CPU consumes 48 watts and at 2Ghz it consumes 40 watts. Yet at 1.6Ghz it consumes only 17 watts! That's a 57.5% drop in power consumption based on only a 20% downclock. Could the XCPU in 360 act similarly? Assuming 3.2Ghz is the cutting edge speed for the CPU (which seems very likely) and the CPU consumes 85W at that speed. Could that mean that a 2.6Ghz version might consume less then half that (under 40W)? Not making any claims, just asking a question.
Given that you could probably trade 1MB of L2 for another PPE core, and that most developers are going to be targeting 512K of L2 or less per core, it doesn't seem very likely that they'd make that choice.Guden Oden said:They'd possibly want to do it [2MB L2] because Nintendo is a very ease-of-development-centric company these days, as opposed to highest peak performance figures.
Given they are instruction level compatible I don't see any problems there. Not to mention 750x series OOOe isn't exactly earthshakingly efficient to begin with.darkblu said:how successfully an in-order cpu will run code meant to run ooo on an cpu only ~4 times slower, i.e. ~2GHz in-order vs. 0.5GHz out-of-order.
Fafalada said:Given they are instruction level compatible I don't see any problems there. Not to mention 750x series OOOe isn't exactly earthshakingly efficient to begin with.
Still, if Nintendo opts for in-order CPU I'll be kinda dissapointed. Don't see the reasoning for 2MB of cache either, I'd imagine 970FX even on slightly lower clock(1.6Ghz?) with 512-1MB of cache would tend to perform better in game apps.
What if the cache can be locked and used directly like a SPE LS? Could this speed up access beyond normal RAM addressing + cache management? Though at the L2 level the speed won't be there for that to be as beneficial as SPE's LS, and the work will still be being done in the D and I caches. So no, I guess that's a useless idea.Fafalada said:Given they are instruction level compatible I don't see any problems there. Not to mention 750x series OOOe isn't exactly earthshakingly efficient to begin with.
Still, if Nintendo opts for in-order CPU I'll be kinda dissapointed. Don't see the reasoning for 2MB of cache either.