On Wed, Oct 21, 2009 at 01:14:02PM +0100, Ilyes Gouta wrote: > Hi, > > > FlushTextureCache and FlushReadCache are for invalidating the caches on > > the GPU. For CPU caches they may not be enough. Eg. with write back cache > > you would need to to do the write back after a CPU write but before any > > Commit dirty lines before invalidating, right?
Yeah. I suppose you could just do the write back without even invalidating the cache if your hardware allows it. > You're right, I'm using > FlushTextureCache and FlushReadCache off their exact semantics. > > > I don't think you should even try to use FlushTextureCache and > > FlushReadCache for CPU cache management. If you have a custom surface > > pool you could do the cache management there (in Lock/Read/Write). > > Absolutely, and that way it would be even possible to narrow down the > purge/invalidate scale of the CPU cache to just the buffer that's > being affected and not like flushing the entire address space of the > frame buffer, right? Sure. -- Ville Syrjälä syrj...@sci.fi http://www.sci.fi/~syrjala/ _______________________________________________ directfb-dev mailing list directfb-dev@directfb.org http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
