All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Clifton <pcjc2@cam.ac.uk>
To: "intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>, Eric Anholt <eric@anholt.net>
Subject: Increased latency from removal of GEM_THROTTLE in 2D driver
Date: Sat, 06 Nov 2010 01:44:59 +0000	[thread overview]
Message-ID: <1289007899.8333.4.camel@pcjc2lap> (raw)

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 <eric@anholt.net>
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)

             reply	other threads:[~2010-11-06  1:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-06  1:44 Peter Clifton [this message]
2010-11-06  9:14 ` Increased latency from removal of GEM_THROTTLE in 2D driver Chris Wilson
2010-11-08  7:37 ` Eric Anholt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1289007899.8333.4.camel@pcjc2lap \
    --to=pcjc2@cam.ac.uk \
    --cc=eric@anholt.net \
    --cc=intel-gfx@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.