[Intel-gfx] [PATCH] Use buffer objects for binding table and surface-state objects.
xhejtman at ics.muni.cz
Fri Nov 7 10:25:18 CET 2008
On Tue, Nov 04, 2008 at 11:10:47AM -0800, Eric Anholt wrote:
> The performance characteristics of the EXA memory manager are, well,
> bad. It's things like "squared with number of allocations that are
> already in offscreen".
UXA will do better job here?
> Someone could add that debugging, and it might be interesting to look at
> (though I'm really interested in seeing what the whole aperture layout
> looks like, often). Other useful debug info would be to attach names to
> objects in the kernel so our debugging could give us stats on types of
> objects (oh, hey, you're leaking surface state objects).
Well, I looked at the code, libdrm has name of the allocation but it is not
passed to the kernel. So one would have to extend the struct passed through
ioctl so that it contains static char array for the name?
More information about the Intel-gfx