Quote Originally Posted by Luka_Aveiro View Post
So we need more efficient and wider bus-interfaces, so data can flow and not stutter.

Nehalem should bring that along with triple channel, shouldn't it?

But it also brings a problem, if my line of thinking is correct: internal ring-buses should also be wider, in order do deal with so much data, correct?

I mean, what advantage would be having so much bandwidth from CPU to GPU, if the GPU ring-bus isn't able to deal with so much info? Coming to think of that, it surely seems a cause to multi-gpu solutions failure, small ring buses on each gpu, do not allow them to create a fluid data path, does it?
NOw you may understand why R600 had 512-bit memory control. ATI foresaw the problem with so much data in flight, as well as issues in re-syncing the dispatch processor with the new data efficiently.

AMD stepped in and lopped off half of that bus, and stutter is much worse on RV670 than R620 because of it. There are other issues plaguing RV670(powerplay) though, so anything that exhibited behavior like stutter has been singled out now.

Of course, a faster bus may help with stutter, but more importantly, it will get data to the cards much quicker, and when dealing with 4 gpus...this is very important. It's(beating stutter) more about a proper balance to the workload, and with todays hardware, it's easy to end up having a bottleneck fixed, only to have another appear elsewhere!