D3D command stream patches for testing
Vedran Rodic
vrodic at gmail.com
Wed Sep 4 09:30:16 CDT 2013
Hello,
I was not subscribed to wine-devel, so I can't reply to Stefan's mail
directly, but here are some of my observations with Dota 2 on an Intel
HD4000 GPU.
Intel Mesa driver doesn't seem to like glBufferSubData in a way this
patchset uses it.
I get many many messages like these per frame when I enable
INTEL_DEBUG=perf performance feedback of the Intel Mesa driver:
Using a blit copy to avoid stalling on 588b glBufferSubData() to a
busy buffer object.
Using a blit copy to avoid stalling on 480b glBufferSubData() to a
busy buffer object.
Using a blit copy to avoid stalling on 480b glBufferSubData() to a
busy buffer object.
Using a blit copy to avoid stalling on 1104b glBufferSubData() to a
busy buffer object.
Using a blit copy to avoid stalling on 252b glBufferSubData() to a
busy buffer object.
Using a blit copy to avoid stalling on 204b glBufferSubData() to a
busy buffer object.
Using a blit copy to avoid stalling on 192b glBufferSubData() to a
busy buffer object.
Using a blit copy to avoid stalling on 192b glBufferSubData() to a
busy buffer object.
Using a blit copy to avoid stalling on 12b glBufferSubData() to a busy
buffer object.
Using a blit copy to avoid stalling on 12b glBufferSubData() to a busy
buffer object.
I'm not sure how much this really impacts performance, but even with
my Dota 2 wine perf hacks [1] it's not faster than current Wine git
(performance is very similar).
On what hardware did you test this patchset?
[1]: http://vrodic.blogspot.com/2013/08/dota-2-wine-optimization-for-intel-gpus.html
More information about the wine-devel
mailing list