Nicolai Hähnle wrote:
> Am Monday 27 July 2009 02:28:00 schrieb Brian Paul:
>> The GLSL compiler uses a similar memory allocator.  See slang_mem.c.
>> We should probably lift this code up into src/mesa/main/ and rename
>> the functions to make it re-usable in drivers, etc.
> 
> Ah, cool, I missed that.

Would you mind doing the work of lifting slang_mem.[ch] to 
src/mesa/main/mempool.[ch] or similar?


> Do you think that it could be lifted even beyond src/mesa/main/? What if I 
> want to use the memory pool from some Gallium driver?

So far, we've kept Mesa's and Gallium's utility code completely 
separate, even when there's some overlap.  We want to build Gallium 
drivers without Mesa and vice versa so sharing code between Mesa and 
Gallium is tricky.

In this specific case though, Gallium already has a memory pool 
allocator in src/gallium/auxilliary/util/u_mm.[ch].  It's somewhat 
geared toward texture memory allocation but with a little work, I 
think it could be made more generic.

-Brian


------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Mesa3d-dev mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mesa3d-dev

Reply via email to