By using this site, you agree to our Privacy Policy and our Terms of Use. Close
Machiavellian on 16 September 2013
Edit Thread
fatslob-:O said:
Machiavellian said:
ethomaz said:

Machiavellian said:

Since that black line connects directly with the ESRAM, would that not mean that the ESRAM is probably used as a cache for the GPU and thus the CPU can read its contents making the system HUMA capable.

Every APU can do that and it is not hUMA... hUMA means you don't need to refresh the CPU-cache to see how the GPU mem is being used... in any APU I can access the GPU memory but I need to refresh my cache table before that.

That's what mean coehent... you don't need to update your cache table to see the latest updates made by GPU (or vice-versa).

So no... the CPU can access the eSRAM without hUMA... what will make it hUMA is if the CPU-cache table coherent with GPU-cache table for eSRAM... if you need to do a refresh everythime you will access the eSRAM then it is not hUMA... in fact it is NUMA.

Thanks, understood.  So at this time no knows what that black line means besides the CPU has access to the ESRAM.  

I wouldn't go as far as to say it has access to since it didn't list a bandwidth but what ever it is its probably not a bus meaning it probably can't access esram.

Just so I am clear on the diagram, it says that the GPU, CPU, Special Processors All share memory via the MMU which has a synchronized page table.  From my understanding, I thought that is what HUMA is.  Is there something wrong with that description.