[Intel-gfx] FireFox performance regressions XAA -> EXA -> UXA
jcristau at debian.org
Tue Jan 26 11:43:24 CET 2010
On Tue, Jan 26, 2010 at 10:02:22 +0000, Chris Wilson wrote:
> On Tue, 26 Jan 2010 04:38:05 -0500, Clemens Eisserer <linuxhippy at gmail.com> wrote:
> > Hi Chris,
> > Thanks for taking the time.
> > @Chris: With XAA, is rendering really done client-side by firefox?
> > I thought with XAA, xorg simply calls pixman for almost everything,
> > but its still server-side?
> I may be completely wrong, of course. ;-) Unless the server supports
> RENDER, Cairo will create image surfaces and perform the rendering locally,
> and then PutImage the result. I presume that firefox follows cairo's
> strategy, or else Cairo will make a lot of GetImage/PutImage requests to
> work-around the lack of functionality on the server. XAA was designed to
> handle the core drawing protocols, EXA was introduced to handle the new
> RENDER protocol.
Whether the driver uses xaa, exa or uxa should be mostly invisible to
the client though? It doesn't affect whether the server supports the
render extension, just how it's handled internally, so shouldn't change
how cairo does stuff. Or am I missing something?
More information about the Intel-gfx