[PATCH 3/3] sync: Record the associated Drawable for a shm/fd fence

[Keith Packard]

Chris Wilson <chris at chris-wilson.co.uk> writes:

> Alongside DRI3, SHM fences are used to serialise changes to the Pixmap
> shared between the client and the xserver. By recording the associated
> Drawable for a particular fence, the driver can reduce the amount of
> work required for serialisation (i.e. it only has to serialise access to
> one Pixmap, not all).

This seems like a useful change, but the Sync extension specification
says that fences are per-screen and not per-drawable, and that the fence
is triggered "after all rendering from previous requests that affects
resources owned by the fence's screen has completed."

If a Sync Fence object is too heavyweight for dri3, we will need to
create a new resource type that is DRI3 specific and use that instead.

-- 
keith.packard at intel.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 810 bytes
Desc: not available
URL: <http://lists.x.org/archives/xorg-devel/attachments/20140512/c0b440f7/attachment.sig>