|author||Eric Anholt <firstname.lastname@example.org>||2013-12-24 15:11:54 -0800|
|committer||Carl Worth <email@example.com>||2014-01-09 12:24:44 -0800|
i965: Don't do the temporary-and-blit-copy for INVALIDATE_RANGE maps.
We definitely want to fall through to the unsynchronized map case, instead of wasting bandwidth on a copy. Prevents a -43.2407% +/- 1.06113% (n=49) performance regression on aa10perf when teaching glamor to provide the GL_INVALIDATE_RANGE_BIT information. This is a performance fix, which I usually wouldn't cherry-pick to stable. But this was really was just a bug in the code, its presence would discourage developers from giving us the best information they can, and I think we've got fairly high confidence in the unsynchronized map path already. Cc: 10.0 9.2 <firstname.lastname@example.org> Reviewed-by: Kenneth Graunke <email@example.com> (cherry picked from commit f46563fe1c8a5560e4de0adf03e3d8770b7fc734)
Diffstat (limited to 'configure.ac')
0 files changed, 0 insertions, 0 deletions