From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 29972] New: d-r-t /r6xx+: use new style fencing (v2) causes very poor gl perf.
Date: Thu, 2 Sep 2010 06:02:09 -0700 (PDT) [thread overview]
Message-ID: <bug-29972-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=29972
Summary: d-r-t /r6xx+: use new style fencing (v2) causes very
poor gl perf.
Product: Mesa
Version: git
Platform: x86 (IA32)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/DRI/R600
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: lists@andyfurniss.entadsl.com
rv790 PCIE, current git ddx, mesa from yesterday.
Just tried today's updated d-r-t and
/r6xx+: use new style fencing (v2)
is causing very poor gl perf eg. 1 fps in mesa demo tunnel, some demos appear
OK at first but even though they reach refresh rate they glitch for a second
after a while.
exa is also affected - it's slower drawing than the "instant" speed I am used
to eg when switching between metacity workspaces. Seamonkey scrolling with a
page with images is glitchy.
Tiling on/off makes no difference, with without last ddx commit makes no
difference.
git reset --hard d-r-t to the commit before this one is working OK.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2010-09-02 13:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-02 13:02 bugzilla-daemon [this message]
2010-09-03 10:24 ` [Bug 29972] d-r-t /r6xx+: use new style fencing (v2) causes very poor gl perf bugzilla-daemon
2010-09-03 14:56 ` bugzilla-daemon
2010-09-03 16:07 ` bugzilla-daemon
2010-09-04 8:53 ` bugzilla-daemon
2010-09-04 11:45 ` bugzilla-daemon
2010-09-04 12:57 ` bugzilla-daemon
2010-09-05 12:33 ` bugzilla-daemon
2010-09-24 22:23 ` bugzilla-daemon
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=bug-29972-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox