OpenHarmony/third_party_mesa3d
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

intel: Don't bother MI_FLUSHing on glFlush in the DRI2 case.

Browse Source 
We only need it when drawing to the front buffer, which we never do for
DRI2.  No significant performance difference, but the flush is definitely
gone from the end of every batchbuffer.
This commit is contained in:
Eric Anholt
2009-10-26 09:37:53 -07:00
parent fb0084e69e
commit 6eb6a0e9cb
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
src/mesa/drivers/dri/intel/intel_context.c
View File

@@ -484,7 +484,7 @@ intel_flush(GLcontext *ctx, GLboolean needs_mi_flush)
* lands onscreen in a timely manner, even if the X Server doesn't trigger * lands onscreen in a timely manner, even if the X Server doesn't trigger
* a flush for us. * a flush for us.
*/ */
if (needs_mi_flush) if (!intel->driScreen->dri2.enabled && needs_mi_flush)
intel_batchbuffer_emit_mi_flush(intel->batch); intel_batchbuffer_emit_mi_flush(intel->batch);
if (intel->batch->map != intel->batch->ptr) if (intel->batch->map != intel->batch->ptr)