From: Daniel Vetter <daniel.vetter@ffwll.ch>
To: intel-gfx@lists.freedesktop.org
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: [PATCH] libdrm changes to allow exact fence usage accounting
Date: Thu, 22 Apr 2010 22:48:45 +0200 [thread overview]
Message-ID: <1271969327-16945-1-git-send-email-daniel.vetter@ffwll.ch> (raw)
Hi all,
Currently libdrm pessimistically assumes that every tiled bo needs a fence
on 2nd and 3rd gen hw on _every_ aperture space checks. Especially with
execbuf2 this results in needlessly small batchbuffers.
My libdrm patch solves this problem by adding a function to libdrm to
disable all fence accounting. Fence usage can then be checked in the
client, where enough information is available to do it exactly.
Comments highly welcome. And if you like this please merge it - I don't
have commit rights on mesa/libdrm and I'd like someone else's explicit
sign-off on interface changes, anyway.
As an example I've also included a patch to convert xf86-video-intel to
do its own fence accounting. This is just for illustration, that patch is
in no way merge-ready - it's totally killing performance on some cairo
traces. On gvim-0 it even hits the brick-wall and slows it down by a factor
of ten :(
Yours, Daniel
Daniel Vetter (1):
i830 uxa: track fence reg usage exactly
src/i830.h | 13 ++++++-
src/i830_batchbuffer.c | 2 +
src/i830_driver.c | 32 ++++++++++++++++
src/i830_render.c | 12 +++---
src/i830_uxa.c | 95 +++++++++++++++++++++++++++++++++++++++++-------
src/i915_render.c | 13 ++++---
6 files changed, 139 insertions(+), 28 deletions(-)
next reply other threads:[~2010-04-22 20:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-22 20:48 Daniel Vetter [this message]
2010-04-22 20:48 ` [PATCH] intel: allow fence register tracking to be disable Daniel Vetter
2010-04-22 20:48 ` [PATCH] i830 uxa: track fence reg usage exactly Daniel Vetter
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=1271969327-16945-1-git-send-email-daniel.vetter@ffwll.ch \
--to=daniel.vetter@ffwll.ch \
--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.