-[[meta title="A new job, but old performance fixes"]]
+[[!meta title="A new job, but old performance fixes"]]
-[[tag exa performance i965]]
+[[!tag exa performance i965]]
Many readers have heard already, but it will be news to some that I
recently changed jobs. After just short of 4 years with Red Hat, I've
was still just using a single vertex buffer that it allocates
upfront---and a tiny buffer---just big enough for a single rectangle
for a single composite operation. And so the driver was waiting for
-each composite operation to finish before reusing the bugger. And the
+each composite operation to finish before reusing the buffer. And the
change to GEM had made this problem even more noticeable. And Eric
even had a partially-working patch to fix this---simply allocating a
much larger vertex buffer and only doing the sync when wrapping around
a vertex buffer to allocate upfront. And that gives me an excuse to
put in a performance plot:
-[[img vertex_buffers.png]]
+[[!img vertex_buffers.png]]
So the more the better, (obviously), until we get to 256 composite
operations fitting into a single buffer. Then we start losing