jeff_rigby
Member
- Nov 22, 2009
- 67
- 0
- 61
I agree that the ESRAM choice was for GPU NOT GPGPU of which 15 blocks are primarily ARM and Xtensa Stream processors. Xtensa stream processors have their own memory and access main memory or other blocks on the ARM AXI buss as NOC not needing the bandwidth the GPU needs.Ok, I reenter this discussion.
In this interview the ESRAM decision is explained by costs and the requirement to be able to do GPGPU stuff.
http://www.eurogamer.net/articles/digitalfoundry-the-complete-xbox-one-interview
For the PS4 the GPU compute blocks mentioned above are in Southbridge and for the XB1 are the ARM block in the XB1 APU. Both are using Xtensa processors which can emulate a GPU or provide GPU compute or as an accelerator for codecs just as a GPGPU can do except 10-100X more efficiently. "Two of those blocks are graphics related" are the codec encoder and decoder Xtensa accelerators.http://www.eurogamer.net/articles/df-hardware-orbis-unmasked-what-to-expect-from-next-gen-console said:PS4 Additional hardware: GPU-like Compute module, some resources reserved by the OS
"However, there's a fair amount of "secret sauce" in Orbis and we can disclose details on one of the more interesting additions. Paired up with the eight AMD cores, we find a bespoke GPU-like "Compute" module, designed to ease the burden on certain operations. We're assured that this is bespoke hardware that is not a part of the main graphics pipeline but we remain rather mystified by its standalone inclusion, bearing in mind Compute functions could be run off the main graphics cores and that devs could have the option to utilise that power for additional graphical grunt, if they so chose."
Durango additional graphics hardware - "rumours have circulated for quite some time that it is some way behind Orbis, but equally there has been the suggestion that the GPU itself is supplemented by additional task-specific hardware. We could not confirm this, but an ex-Microsoft staffer with a prior relationship with the Xbox team says that two of these modules are graphics-related."
For costs I think you misread.
Power use is stressed multiple times but price only once. Add that the ESRAM block costs more to implement than the difference between DDR3 and GDDR5...at least that was part of the explanation for the XB1 APU having fewer CUs than the PS4 which is said to cost less to produce.Nick Baker: Yeah, I think that's right. In terms of getting the best possible combination of performance, memory size, power, the GDDR5 takes you into a little bit of an uncomfortable place. Having ESRAM costs very little power and has the opportunity to give you very high bandwidth. You can reduce the bandwidth on external memory - that saves a lot of power consumption as well and the commodity memory is cheaper as well so you can afford more. That's really a driving force behind that. You're right, if you want a high memory capacity, relatively low power and a lot of bandwidth there are not too many ways of solving that.
If your design requires the ARM block to be inside the APU like current and future AMD designs so the work on the XB1 can be used with future AMD APUs and you don't have access to HBM, the only choice is to have ESRAM and DDR3.
Why did the PS4 move it's ARM block out of the APU to Southbridge with it's own DDR3 memory? Power use. That was more of a break with AMD APU designs while the XB1 is more future AMD design but without the "25X20 power efficiencies" that are coming by 2020.
The ARM blocks are also the DRM security blocks; Codec, Encryption, Keys, Player, output buffer and more. They are key to media streaming both in the home and from the cloud. Access to those blocks is limited to APIs and both Sony and Microsoft are still writing the OS that uses those blocks. Playready ND is still a work in progress. Playready ND is the 4K version of DTCP-IP WMDRM10 which content owners trust only for 1080i and lower media.
Last edited: