code bloat [was Re: Semaphore assembly-code bug]

[Adam Jackson]

On Monday 01 November 2004 10:35, Roland Mainz wrote:
> Lee Revell wrote:
> > Um I don't think chucking X is the answer.  The problem is that it's
> > embarassingly slow compared to any modern GUI.  If the display were as
> > snappy as WinXP I don't care if it's 200MB.  On my desktop I constantly
> > see windows redrawing every freaking widget in situations where XP would
> > just blit from an offscreen buffer or something.
>
> That sounds more like that backing-store is turned off in your
> Xserver... ;-/

Backing store and XAA are mutually exclusive.  If you do an XAA-accelerated 
operation to a region with a backing store, then you invalidate the backing 
store.  Woops.

XAA goes to a lot of effort to accelerate the primitives no one uses, and 
desperately needs to be taken out behind the barn and shot.  KAA accelerates 
probably a tenth of the ops XAA accelerates, but they're the right tenth so 
the code is simpler and the performance way better.

So, yeah, chucking X is not the answer, but chucking XAA probably is.

- ajax
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://lists.x.org/archives/xorg/attachments/20041101/076f029f/attachment.pgp>