From: Chris Wilson <chris@chris-wilson.co.uk>
To: Peter Clifton <pcjc2@cam.ac.uk>,
intel-gfx@lists.freedesktop.org, Eric Anholt <eric@anholt.net>
Subject: Re: Increased latency from removal of GEM_THROTTLE in 2D driver
Date: Sat, 06 Nov 2010 09:14:45 +0000 [thread overview]
Message-ID: <5b55a1$ij6d8h@fmsmga002.fm.intel.com> (raw)
In-Reply-To: <1289007899.8333.4.camel@pcjc2lap>
On Sat, 06 Nov 2010 01:44:59 +0000, Peter Clifton <pcjc2@cam.ac.uk> wrote:
> 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.
Do you get a similar effect with the THROTTLE in the ddx and a recent
kernel (2.6.37-rc1 or drm-intel-next)? Those kernels should only penalize
the caller of THROTTLE and so X should not end up blocking your app.
I can feel a new tracepoint coming: throttle-begin, throttle-end.
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2010-11-06 9:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-06 1:44 Increased latency from removal of GEM_THROTTLE in 2D driver Peter Clifton
2010-11-06 9:14 ` Chris Wilson [this message]
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='5b55a1$ij6d8h@fmsmga002.fm.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=eric@anholt.net \
--cc=intel-gfx@lists.freedesktop.org \
--cc=pcjc2@cam.ac.uk \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox