Chris Wilson <[email protected]> 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. -- [email protected]
pgpNYQIUTXhtk.pgp
Description: PGP signature
_______________________________________________ [email protected]: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: http://lists.x.org/mailman/listinfo/xorg-devel
