[PATCH] drm/radeon/kms: optimize CS state checking for r100->r500

2011-02-13 Thread Marek Olšák
On Sat, Feb 12, 2011 at 7:21 PM, Marek Ol??k wrote: > The colorbuffer, zbuffer, and texture states are checked only once when > they get changed. This improves performance in the apps which emit > lots of draw packets and few state changes. > > This drops performance in glxgears by a 1% or so, bu

[PATCH] drm/radeon/kms: optimize CS state checking for r100->r500

2011-02-12 Thread Marek Olšák
The colorbuffer, zbuffer, and texture states are checked only once when they get changed. This improves performance in the apps which emit lots of draw packets and few state changes. This drops performance in glxgears by a 1% or so, but glxgears is not a benchmark we care about. The time spent in

Re: [PATCH] drm/radeon/kms: optimize CS state checking for r100->r500

2011-02-12 Thread Marek Olšák
On Sat, Feb 12, 2011 at 7:21 PM, Marek Olšák wrote: > The colorbuffer, zbuffer, and texture states are checked only once when > they get changed. This improves performance in the apps which emit > lots of draw packets and few state changes. > > This drops performance in glxgears by a 1% or so, bu

[PATCH] drm/radeon/kms: optimize CS state checking for r100->r500

2011-02-12 Thread Marek Olšák
The colorbuffer, zbuffer, and texture states are checked only once when they get changed. This improves performance in the apps which emit lots of draw packets and few state changes. This drops performance in glxgears by a 1% or so, but glxgears is not a benchmark we care about. The time spent in