I've been thinking a bit about this, and while I think Ian's work on the memory manager has merit I'm starting to think we are really putting the cart before the horse in some ways....
My thinking on this is that the memory manager needs to live in libdrm, not like the current bits in Xorg DDX, bits in Mesa, bits in kernel, all code should be in libdrm and the kernel userspace split should be hidden behind an interface, the internals of the memory manager whether it be the dumb via/sis manager or Ian's log based system shouldn't in theory matter if it can be hidden behind the libdrm interface.. So I've modified http://dri.freedesktop.org/wiki/DriMemoryManagerDesign and added a Memory Manager Interface section with some initial thoughts, in the hope that maybe some discussion occurs on it, in theory we should be able to implement the current memory management schemes using the interface, I'm sure we probably need some more entrry points.. and maybe alloc region needs to be able to specify some alignment.. or a callback if the region has becomed swapped out... Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie Linux kernel - DRI, VAX / pam_smb / ILUG ------------------------------------------------------- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today * Register for a JBoss Training Course Free Certification Exam for All Training Attendees Through End of 2005 Visit http://www.jboss.com/services/certification for more information -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
