|
WereKitten said: Yes, that's what I read. But an ALU is an ALU... there's no magic that will make it crunch double the instructions per cycle only because you tag one as graphic and the other as compute. The way I read that is that, going back to the vgleak document about the increased number of queues, you'll be able to keep the CUs occupied with graphic and computing tasks in parallel, without any big scale mode switch, resulting in a greater efficiency. A Flop is a Flop... if it were like you said, those CUs would just have double the maximum theoretical Flop throughput and it would not make any sense to mark them as 1.8Tflops. They would just be indicated as 3.6Tflops because that's how many operations per second they would be able to crunch in the best scenario. |
Semms reasonable... and the parallel thing the PC can't do... what that's means?
