Re: [Dri-devel] r200 PCI Slowness

2003-12-06 Thread Chris Ison
> You can run without software interrupts or usleeps with > > fthrottle_mode=0 glxgears > ok, doing this for both glxgears and quakeforge reveals interesting results.It also has a 0.13% increase in FPS with glxgears glxgears ... samples %image name app namesymbol name 173692

Re: [Dri-devel] r200 PCI Slowness

2003-12-06 Thread Michel Dänzer
On Sat, 2003-12-06 at 08:49, Chris Ison wrote: > After a couple of kernel recompiles I got oprofile to work, and it was > reporting that most of its time was spend in default_idle for both > glxgears and qw-client-glx (from QuakeForge CVS). > > After speaking to one of the oprofile ppl, they seem

Re: [Dri-devel] r200 PCI Slowness

2003-12-05 Thread Mike Mestnik
I'm not 100% sure but I know the + and - show whether the bit is set or not. If the bit is set then that means the feature is on, so the driver MUST use it or there should be problems. By problems I mean crashes or rendering errors, more than it just being slow. --- Chris Ison <[EMAIL PROTECTE

Re: [Dri-devel] r200 PCI Slowness

2003-12-05 Thread Chris Ison
I don't know if its relevent, but just a couple of observations to do with glxgears that "may" help pinpoint whats going on. glxgears normally does about 250fps, if I enlarge its windows to cover the the entire screen this drops to about 80fps, but if I cover the window it jumps up to about 1270fp

Re: [Dri-devel] r200 PCI Slowness

2003-12-05 Thread Chris Ison
On Sat, 2003-12-06 at 07:57, Mike Mestnik wrote: > lspci -vvv > That just tells me the card is capable of using it, doesn't actually tell my if DRI is taking advantage of it. With and without DRI installed it tells me the same thing Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- Par

Re: [Dri-devel] r200 PCI Slowness

2003-12-05 Thread Mike Mestnik
lspci -vvv --- Chris Ison <[EMAIL PROTECTED]> wrote: > After a couple of kernel recompiles I got oprofile to work, and it was > reporting that most of its time was spend in default_idle for both > glxgears and qw-client-glx (from QuakeForge CVS). > > After speaking to one of the oprofile ppl, the

[Dri-devel] r200 PCI Slowness

2003-12-05 Thread Chris Ison
After a couple of kernel recompiles I got oprofile to work, and it was reporting that most of its time was spend in default_idle for both glxgears and qw-client-glx (from QuakeForge CVS). After speaking to one of the oprofile ppl, they seem to think that this is as much as I will get cause it appe