From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 34493] New: r600g performance regression introduced by 467023e8 (Marek Olšák: r600g: use the same upload buffer for vertices, indices, and constants)
Date: Sat, 19 Feb 2011 22:45:10 -0800 (PST) [thread overview]
Message-ID: <bug-34493-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=34493
Summary: r600g performance regression introduced by 467023e8
(Marek Olšák: r600g: use the same upload buffer for
vertices, indices, and constants)
Product: Mesa
Version: git
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r600
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: dawitbro@sbcglobal.net
As detailed in Comment 6 of bug 34156, I found this regression in Mesa 7.11-git
while trying to pin down another performance regression a few commits earlier.
I was able to create a local branch where I was able to reverts 4 commits from
a series by Henri Verbeet, which restored performance to the level which
existed before that series was introduced. Performance remained high after the
4 reverts until commit 467023e8 was introduced.
Reverting this commit (in addition to the 4 mentioned in the other bug report:
077c448d, 7687eaba, 1fa95c7f, and a77e813d) restores performance. All further
Mesa commits through the next 10 days (up to the HEAD I have currently, which
is fd8d4b32 of Feb. 18) are working fine.
I am using r600g on 64-bit Linux, with the following hardware + software:
Hardware: Radeon HD 5750 (Evergreen JUNIPER)
Software:
kernel 2.6.37 (+ radeon cherry-picks from drm-fixes)
libdrm 2.4.23
xorg-server 1.9.4
xf86-video-ati 6.14.0
If I can provide any further info/assistance, just let me know.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2011-02-20 6:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-20 6:45 bugzilla-daemon [this message]
2011-03-01 22:09 ` [Bug 34493] r600g performance regression introduced by 467023e8 (Marek Olšák: r600g: use the same upload buffer for vertices, indices, and constants) bugzilla-daemon
2011-03-01 23:12 ` bugzilla-daemon
2011-03-01 23:45 ` bugzilla-daemon
2011-03-02 1:01 ` bugzilla-daemon
2011-03-02 1:19 ` bugzilla-daemon
2011-03-02 4:01 ` bugzilla-daemon
2011-04-12 3:15 ` bugzilla-daemon
2012-02-22 18:08 ` 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-34493-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 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.