From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter Clifton Subject: Increased latency from removal of GEM_THROTTLE in 2D driver Date: Sat, 06 Nov 2010 01:44:59 +0000 Message-ID: <1289007899.8333.4.camel@pcjc2lap> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from ppsw-50.csi.cam.ac.uk (ppsw-50.csi.cam.ac.uk [131.111.8.150]) by gabe.freedesktop.org (Postfix) with ESMTP id 8B5AB9E7AF for ; Fri, 5 Nov 2010 18:45:02 -0700 (PDT) List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org Errors-To: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org To: "intel-gfx@lists.freedesktop.org" , Eric Anholt List-Id: intel-gfx@lists.freedesktop.org I've been playing with my app again, and whilst it seems a tiny bit faster in benchmarks, since the 2D driver change: commit 8ff37667bf864b771d16a58fc5041cb48408b6a8 Author: Eric Anholt Date: Tue Nov 2 10:36:03 2010 -0700 Remove the intermittent GEM_THROTTLE call. I've noticed the latency / interactivity is WAY down, and I've also had intermittent GPU hangs whilst benchmarking which I'd never seen before. It might be unrelated (as I'm running a back-ported drm-intel-next, and just pulled it up to date), but for a quick check, I just reverted to a previous 2D driver just prior to the above commit, and interactivity has improved a lot (I don't have a number for it, just from testing). Presumably this says something bad about my app, or its benchmarking code. Any clues as to what that is? Without the commit, I can use other X11 apps whilst my PCB program is benchmarking. With it, the X11 server graphics almost completely freeze up. -- Peter Clifton Electrical Engineering Division, Engineering Department, University of Cambridge, 9, JJ Thomson Avenue, Cambridge CB3 0FA Tel: +44 (0)7729 980173 - (No signal in the lab!) Tel: +44 (0)1223 748328 - (Shared lab phone, ask for me)