Re: Swapbuffers [was: Re: DRI2 and lock-less operation]

On Wed, Nov 28, 2007 at 12:43:18PM +0100, Stephane Marchesin wrote: > > This is what I want to do too. Especially since in the nvidia case we don't > have the issue of routing vblank interrupts to user space for that. > > So, the only issue I'm worried about is the latency induced by this > appro

Re: Swapbuffers [was: Re: DRI2 and lock-less operation]

Stephane Marchesin wrote: > On 11/28/07, *Keith Whitwell* <[EMAIL PROTECTED] > > wrote: > > > In my ideal world, the entity which knows and cares about cliprects > should be the one that does the swapbuffers, or at least is in control > of the process. That

Re: Swapbuffers [was: Re: DRI2 and lock-less operation]

On 11/28/07, Keith Whitwell <[EMAIL PROTECTED]> wrote: > > > In my ideal world, the entity which knows and cares about cliprects > should be the one that does the swapbuffers, or at least is in control > of the process. That entity is the X server. > > Instead of tying ourselves into knots trying

Swapbuffers [was: Re: DRI2 and lock-less operation]

Kristian Høgsberg wrote: > On Nov 27, 2007 11:48 AM, Stephane Marchesin > <[EMAIL PROTECTED]> wrote: >> On 11/22/07, Kristian Høgsberg <[EMAIL PROTECTED]> wrote: > ... >>> It's all delightfully simple, but I'm starting to reconsider whether >>> the "lockless" bullet point is realistic. Note, the