By using this site, you agree to our Privacy Policy and our Terms of Use. Close
ethomaz said:
Adinnieken said:
ethomaz said:

MS needed to create your own tech because I can't see the hUMA that AMD implemented working together with eSRAM and DataMoves... it's not only CPU and GPU accesing the same data pool in memory... it's CPU, GPU and DataMoves accesing the same data pool in memory or eSRAM.

The MS solution seems to be more complex to be implemented than the AMD hUMA.

No, not really.

The Xbox One's memory architecture:

SOURCE

I can't really understand this graph since the first time I saw it... seems like they tried to add stuffs to make easy or there are something missing because I'm sure all MoveEngine have direct access to 8GB DDR3 and ESRAM (they are created to copy data from DDR3 to eSRAM - and vice versa - without use CPU or GPU).

I don't know how the MS version of the "hUMA" works but at least it need to handle the CPU, GPU and DataMoves shared access in DDR3... so MS needs to customize it because the AMD version just handle CPU and GPU.

I thought the VGLeaks image was taken from documentation, but it appears it is thier understanding of how it works based on what they concluded from the documentation.