On 06/25/2015 03:33 AM, Andrew Brygin wrote:
Given that it is a unified driver it sounds like we may be want
to disable this code path when on windows at least for NV but I guess we
may also want to validate that on some other cards - from Nvidia - to
see if it is a driver or h/w limitation.
Probably, we should to run the text benchmarks on relatively big set
of windows
machines, and if we see that good performance of glCopyTexSubImage()
is sooner
a rule than an exception, then we can just disable the new code path
on windows.
Wat do you think?
Yes.
Also it occurs to me to wonder why we have not had the same performance
complaints
when using D3D on Windows .. different APIs but they have the same
limitation.
It would be interesting to know if objective performance tests on the
same hardware
show that Windows users are more forgiving or it really is not a problem
there ...
-phil.
