accelerated indirect rendering [was Re: Disable xterm and XRX...]

[Owen Taylor]

On Mon, 2005-01-24 at 15:02 -0500, Adam Jackson wrote:
> On Monday 24 January 2005 14:33, Keith Packard wrote:
> > Around 19 o'clock on Jan 24, Keith Whitwell wrote:
> > > It doesn't refer to any of the serverside stuff, especially not the
> > > software indirect renderer which is built into (I think) dri.a and which
> > > contains basically the whole mesa source tree.  The right way to remove
> > > this last dependency is to get indirect rendering handled (one way or
> > > another) by the hardware acclerated clientside code.
> >
> > I'm not concerned about the server-side software rendering code; that can
> > provide stale GL support for all the value it has to real applications; to
> > some extent, it would actually be a feature to use pure client-side
> > rendering instead as it's faster...
> 
> Can be.  Isn't always.  Depending on what card and the phase of the moon I can 
> get better performance out of indirect GLX versus Mesa's X11 driver.  At any 
> rate hardware indirect is the better way to go.
> 
> The value in accelerated indirect is in things like DMX, where AIGLX gets you 
> accelerated GL on every head.  Also this makes cairo apps over the network 
> Not Suck.

In my current thinking, it's also the right way to do a GL-based
compositing manager; since the primary texture sources (window pixmaps)
are server-side resouces, using indirect rendering saves a lot of 
bandwidth and synchronization.

Regards,
						Owen

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <http://lists.x.org/archives/xorg/attachments/20050124/2e7037a4/attachment.pgp>