From: Dave A. <ai...@li...> - 2005-07-28 21:30:57
|
Hi, (mainly KeithW) I'm looking at the current i915 mem manager which shares the LRU texture area with client side textures which would be useful in my system, as I want to have the AGP texturing but also some client side textures... a) should it work? (given I don't really care about backwards compat) b) do I still need to use glxMesaAllocateMemory and friends? Regards, Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie Linux kernel - DRI, VAX / pam_smb / ILUG |
From: Keith W. <ke...@tu...> - 2005-07-29 06:54:01
|
Dave Airlie wrote: > Hi, (mainly KeithW) > > I'm looking at the current i915 mem manager which shares the LRU texture > area with client side textures which would be useful in my system, as I > want to have the AGP texturing but also some client side textures... > > a) should it work? (given I don't really care about backwards compat) > b) do I still need to use glxMesaAllocateMemory and friends? It'd probably work fine, it's still a bit of a hack though. Maybe it's time to really do the work on a proper manager? I'm at a point where I can put a bit of time into that. Keith |
From: Dave A. <ai...@li...> - 2005-07-29 08:38:28
|
> > a) should it work? (given I don't really care about backwards compat) > > b) do I still need to use glxMesaAllocateMemory and friends? > > It'd probably work fine, it's still a bit of a hack though. Maybe it's time > to really do the work on a proper manager? I'm at a point where I can put a > bit of time into that. Oh I know it'd be a hack, but it would be for a job I'm working on, its definitely not something I'd like to give back... I'm definitely thinking we need to take Ian's DriMemoryManagerDesign document and start thinking throught the issues.. it needs to be expanded to be able to manage all graphics memory, VRAM and AGP, including framebuffers and all that stuff, every driver using should allocate via it, no more X 2D memory manager and all that .. being able to resize framebuffers etc by dropping all the clobberable blocks, and moving other stuff around would be a good start... Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie Linux kernel - DRI, VAX / pam_smb / ILUG |
From: Dave A. <ai...@li...> - 2005-07-30 05:37:40
|
> > I'm definitely thinking we need to take Ian's DriMemoryManagerDesign > document and start thinking throught the issues.. it needs to be expanded > to be able to manage all graphics memory, VRAM and AGP, including > framebuffers and all that stuff, every driver using should allocate via > it, no more X 2D memory manager and all that .. being able to resize > framebuffers etc by dropping all the clobberable blocks, and moving other > stuff around would be a good start... I've sort of said it above, but just to re-iterate I know longer think we are looking at a DRI Memory Manager, this should really be a VRAM memory manager for everything, not just 3d objects... I think projects like DirectFB should also be able to use it.. and even fbdev driver should interact with it if they want... i.e. if anything in the system wants some VRAM it must go through this.. this will probably change where we want to place the kernel/user boundary, I think Ians current design is too biased towards userspace and DRI requirements in its current form... Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie Linux kernel - DRI, VAX / pam_smb / ILUG |