Performance change from X in Fedora Core 4 to Fedora Core 5

Carsten Haitzler (The Rasterman) raster at rasterman.com
Mon Jul 10 18:04:08 PDT 2006


On Mon, 10 Jul 2006 15:10:24 -0700 Keith Packard <keithp at keithp.com> babbled:

> On Mon, 2006-07-10 at 22:41 +0100, Felix Bellaby wrote:
> 
> > What we should be aiming to do is avoid the generation of damage reports
> > until we are ready to display the finished drawing. The compositor will
> > ignore drawing operations until the damage is reported, allowing the off
> > screen pixmap to act as a buffer. Then the compositor will set about
> > displaying the pixmap when the damage is reported, effectively
> > performing a buffer swap. Compositors already do this automatically so
> > you are not putting any extra burden on them whatsoever.
> 
> Oh, that's an interesting notion, and it should be reasonably easy to
> implement as well. Just some kind of 'damage suspend'/'damage release'
> requests should be more than sufficient here. Adding that to Damage
> itself might be a reasonable option. Fixing Composite to let
> applications know when they are redirected might also be nice; right now
> there's no indication at all.

definitely - but see my other mail. you have a problem of half-drawn stuff when
an update happens... :( but i would definitely like the above features - it
would allow for a much more organised draw flush :)

-- 
------------- Codito, ergo sum - "I code, therefore I am" --------------
The Rasterman (Carsten Haitzler)    raster at rasterman.com
裸好多
Tokyo, Japan (東京 日本)



More information about the xorg mailing list