On Wed, Mar 26, 2003 at 09:08:51AM -0800, Ian Romanick wrote: > Michel Dänzer wrote: > >On Mit, 2003-03-26 at 08:45, Philip Brown wrote: > > > >>Video mem is a core X server resource, and should be reserved through the > >>core server, always. > > > >Actually, I thought we're talking about a scheme where the server is > >only a client of the DRM memory manager. > > Yes. It would be a lot easier if more was implemented in the DRM, but > we don't want more in the kernel then is absolutely required. As it > stands, the DRM only implements the mechanism for paging out blocks to > "secondary" storage (i.e., system memory, AGP, etc.). All of the > mechanism for allocating memory to applications and the policy for which > blocks get paged and reclaimed happens in user-mode.
Did you ever got to speak with the XFree86 folk about this, it seems that the new XAA implementation will abstract memory management, and let the (X) driver handle this. Ideally, you would have the little bit of code in the kernel module and a library on top of that which could be used by the DRI, but also by the X driver or even other userland stuff (like DirectFB for example). > I've been working on a prototype implementation of the user-mode code > for the last week. My current estimation is that the user-mode code > will be 3 to 4 times as large as the kernel code. I should have a > pthreads based framework with a mock up of the kernel code ready to Would this pthread using userland pthread using code be usable in the X driver ? Friendly, Sven Luther ------------------------------------------------------- This SF.net email is sponsored by: The Definitive IT and Networking Event. Be There! NetWorld+Interop Las Vegas 2003 -- Register today! http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
