> > glxgears uses 40% of the CPU in both classic and gem. Note that the gem > version takes about 20 seconds to reach a steady state -- the gem driver > isn't clearing the gtt actively and so glxgears gets far ahead of the > gpu. > > My theory is that this shows that using cache-aware copies from a single > static batch buffer (as gem does now) improves cache performance and > write bandwidth.
I'm still confused by your test setup... Stepping back from cache metaphysics, why doesn't classic pin the hardware, if it's still got 60% cpu to burn? I think getting reproducible results makes a lot of sense. What hardware are you actually using -- ie. what is this laptop? Keith ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ -- _______________________________________________ Dri-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dri-devel
