summaryrefslogtreecommitdiff
path: root/src/intel_driver.c
diff options
context:
space:
mode:
authorEric Anholt <eric@anholt.net>2010-11-02 10:36:03 -0700
committerEric Anholt <eric@anholt.net>2010-11-02 10:58:46 -0700
commit8ff37667bf864b771d16a58fc5041cb48408b6a8 (patch)
treec10931946d1aec55418a1cda09678d3bc47f9613 /src/intel_driver.c
parent540c5742186c26c3aeccb7b5d3ff0f374722a20c (diff)
Remove the intermittent GEM_THROTTLE call.
This is a holdover from early GEM work when we weren't syncing on the DRI client side. It would keep clients from getting too far ahead and killing their interactivity, by bringing everyone to a halt when anyone was too far ahead. Now, GL clients throttle themselves to avoid the problem, and it turns out that in the case that they don't (long rendering to buffers with no swap), this actually reduces X Server interactivity: instead of lagging of X rendering behind input, you get no response for seconds at a time, then a burst of rendering, then nothing again. Reported by ajax. Tested with moving a window while running cairo-perf-trace on the GL backend (improvement) and X backend (no significant change in responsiveness).
Diffstat (limited to 'src/intel_driver.c')
-rw-r--r--src/intel_driver.c3
1 files changed, 0 insertions, 3 deletions
diff --git a/src/intel_driver.c b/src/intel_driver.c
index 01c8c1bf..fd518999 100644
--- a/src/intel_driver.c
+++ b/src/intel_driver.c
@@ -688,9 +688,6 @@ I830BlockHandler(int i, pointer blockData, pointer pTimeout, pointer pReadmask)
intel->BlockHandler = screen->BlockHandler;
screen->BlockHandler = I830BlockHandler;
- if (scrn->vtSema == TRUE)
- drmCommandNone(intel->drmSubFD, DRM_I915_GEM_THROTTLE);
-
intel_uxa_block_handler(intel);
intel_video_block_handler(intel);
}