From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 27297] New: Gallium R300g - xscreensaver "endgame" hack runs much slower than under classic Mesa.
Date: Wed, 24 Mar 2010 15:34:17 -0700 (PDT) [thread overview]
Message-ID: <bug-27297-502@http.bugs.freedesktop.org/> (raw)
http://bugs.freedesktop.org/show_bug.cgi?id=27297
Summary: Gallium R300g - xscreensaver "endgame" hack runs much
slower than under classic Mesa.
Product: Mesa
Version: git
Platform: x86 (IA32)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/DRI/r300
AssignedTo: dri-devel@lists.sourceforge.net
ReportedBy: rankincj@googlemail.com
Using Mesa from git and Radeon 9550 (RV350). Under "classic" Mesa, the
"endgame" OpenGL hack from xscreensaver runs at between 15 fps and 20 fps.
However, it only runs at between 3 fps and 5 fps under Gallium. The CPU load
under Gallium is considerably higher too.
--
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
--
next reply other threads:[~2010-03-24 22:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-24 22:34 bugzilla-daemon [this message]
2010-03-25 1:57 ` [Bug 27297] Gallium R300g - xscreensaver "endgame" hack runs much slower than under classic Mesa bugzilla-daemon
2010-03-25 13:48 ` bugzilla-daemon
2010-03-26 12:50 ` bugzilla-daemon
2010-03-27 21:20 ` [Bug 27297] [r300g] " bugzilla-daemon
2010-03-27 21:20 ` 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-27297-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.sourceforge.net \
/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.