> It should be the responsibility of the memory manager. If anything wants > to access the memory it would call lock() and when it's done with the > memory it calls unlock(). That's exactly how DirectFB's memory manager > works.
In an ideal world ... However, since we are planning to move the memory manager to the kernel, that would mean a kernel access (syscall, ioctl, whatever...) twice per access to AGP memory. Not realistic. The case of the CP ring is easy to deal with by the macros we have there already and it would be kernel-kernel. But it would be a hit for a lot of other things I suppose. Ben. ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
