On Wed, 2008-05-14 at 21:41 +0200, Thomas Hellström wrote: > As you've previously mentioned, this requires caching policy changes and > it needs to be used with some care.
I did't need that in my drivers as GEM handles the WB -> GPU object transfer already. Object mapping is really the least important part of the system; it should only be necessary when your GPU is deficient, or your API so broken as to require this inefficient mechanism. I suspect we'll be tracking 965 performance as we work to eliminate mapping, we should see a steady increase until we're no longer mapping anything that the GPU uses into the application's address space. -- [EMAIL PROTECTED]
signature.asc
Description: This is a digitally signed message part
------------------------------------------------------------------------- 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 Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel