You can only read a 170gb/s as a combination of both memory clients, 102 + 62.
But you can only write back at 102 maximum.
Its all very vague.
It can certainly read ESRAM and read DDR3 concurrently.All the Move Engine is doing there is moving/copying data between the DDR3 RAM and/or ESRAM. It uses the bandwidth of the DDR3 RAM and/or ESRAM to achieve this; depends on how it is moving/copying the data around.
Yes, it does it in parallel with computation of the GPU but at a slower throughput and at the sacrifice of bandwidth if the memory is being used by the GPU at the time. This doesn't mean or suggest that the GPU can write to the ESRAM and read the DDR3 RAM concurrently.
The 360, can read from GDDR and write concurrently to the EDRAM, thats why its so dam good as a GPU, because it has zero wait states for the memory. Perhaps concurrently is a little of a misnomer, lets just say so dam fast it may as well be concurrent.
It still looks like two separate buss's...
The move engines can move data from EDRAM to EDRAM or DDR to DDR, without messing up the the GPU's own write features to the other.
ie. GPU->EDRAM, separate to GPU->DDR.
Results 1 to 25 of 73
- Join Date
- May 2006
- Down Under
- Rep Power
- 167,413 (0 Banked)
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)