On Sat, 29 Jan 2005 04:13:08 -0500, Daniel Phillips <[EMAIL PROTECTED]> wrote: > On Friday 28 January 2005 14:20, Timothy Miller wrote: > > It occurs to me that there might be a pathelogical case where many > > clients start competing for card memory to the point that an active > > client's texture gets kicked out between the time it's requested in > > and when it gets around to using it. We may need some sort of > > locking mechanism. When you request to lock a texture, it gets > > swapped in (if it isn't already) and gets locked. When you unlock > > it, it may get swapped out. What happens then is that if we run out > > of memory, some clients will block and get sorta queued up. It > > sounds bad, but really the software overhead for this is trivial > > compared to all the swapping going on. > > 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. _______________________________________________ Open-graphics mailing list [email protected] http://lists.duskglow.com/mailman/listinfo/open-graphics List service provided by Duskglow Consulting, LLC (www.duskglow.com)
