> You know, I didn't think about this until just now. I was thinking > about locking the pages and then blocking if there's a write. But I > wonder... we could set up CoW so that if the process tries to write to > a page of a texture that is in the process of being uploaded, the page > gets copied, the copy assigned to the process, and the original gets > freed when the upload is done. This is a compromise between up-front > copying and blocking until the copy is done, because not all of it > will necessarily get copied. The various performance impacts will > have to be considered.
I'm not sure the performance impact of the various MMU operations won't make it worthless if it's only about dealing with an upload, but heh, maybe ... I was thinking more about context switching, while may require also switching textures in/out vram. But then, again, we may not need MMU tricks provided that GL API allows us to do things transparently enough (I don't know enough there). In the case of things like fb objects, that's a different matter though. Ben. _______________________________________________ Open-graphics mailing list [email protected] http://lists.duskglow.com/mailman/listinfo/open-graphics List service provided by Duskglow Consulting, LLC (www.duskglow.com)
