[Intel-gfx] [PATCH] Use buffer objects for binding table and surface-state objects.

Eric Anholt eric at anholt.net
Fri Nov 7 19:59:21 CET 2008


On Fri, 2008-11-07 at 10:25 +0100, Lukas Hejtmanek wrote:
> 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?

EXA with CreatePixmap hook (we'll be doing that shortly) or UXA.

> > 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?
> 
-- 
Eric Anholt
eric at anholt.net                         eric.anholt at intel.com


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
URL: <http://lists.freedesktop.org/archives/intel-gfx/attachments/20081107/8b056f08/attachment.pgp>


More information about the Intel-gfx mailing list