On Sat, 29 Jan 2005 14:19:04 -0500, Daniel Phillips <[EMAIL PROTECTED]> wrote: > On Saturday 29 January 2005 11:47, Timothy Miller wrote: > > On Sat, 29 Jan 2005 04:13:08 -0500, Daniel Phillips > <[EMAIL PROTECTED]> wrote: > > > A per-texture use count, incremented at the beginning of processing > > > a textured triangle (including possibly DMAing the texture from the > > > host) and decremented at the end? > > > > There are all sorts of algorithms the memory manager can use for > > deciding which textures can be swapped out. > > Hi Timothy, > > You need to know with certainty whether a texture is currently "pinned" > by being referenced by an object currently in the rendering pipeline. > I don't see any practical way to do that other than a use count. > > This logic doesn't have to be in the card though.
"pinning" a texture would happen as sortof a lock wheneven a client is submitting commands. Like, the DMA request packet could include a list of images to lock. Something like that. The idea is that whenever drawing is going to happen, the client has to ask for exclusive access to them and then unlock when idle. _______________________________________________ Open-graphics mailing list [email protected] http://lists.duskglow.com/mailman/listinfo/open-graphics List service provided by Duskglow Consulting, LLC (www.duskglow.com)
