-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Keith Whitwell wrote: > > Extending the memory manager would involve adding an ability to lock and > unlock surfaces to VRAM/AGP addresses - this would require kernel > interaction I guess. The driver would have to lock the surfaces then be > free to submit commands to the ring, then explicitly unlock the > surfaces. This is actually a pretty nasty approach - it makes it very > hard to deal with low-memory situations - it's impossible to kick out > another processes allocations.
This was similar to how I had designed the memory manager that I never finished. In order to make this work, you have to set a fence when you unlock the surface. You can still kick out surfaces that we locked by another process, but you have to wait until the fence has past. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) iD8DBQFFDxHFX1gOwKyEAw8RAgK8AKCLZb0FXQMF7cFP4fWxdTjIb+aLwQCcClRk yk/LjKRuECunVbP8/EFRxfk= =YUsT -----END PGP SIGNATURE----- ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
