<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - We need fences support in Wayland compositors" href="https://bugs.freedesktop.org/show_bug.cgi?id=98766#c11">Comment # 11</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - We need fences support in Wayland compositors" href="https://bugs.freedesktop.org/show_bug.cgi?id=98766">bug 98766</a> from <a class="email" href="mailto:jajones@nvidia.com" title="James Jones <jajones@nvidia.com>"> James Jones</a> <pre>Not proposing baking in any particular backend assumptions or debating whether Khronos or Linux assumptions are better, but rather I was indirectly suggesting a few modifications to make the overall extension less dependent on any particular type, and allow persistence -Register fences as a new wayland object type prior to actual attachment, similar to how wl_surface abstracts DRM/shm/etc. This makes persistence easy when the underlying objects support it, and since apparently wayland object creation is cheap, shouldn't add appreciable overhead where persistence doesn't matter or doesn't work. -Explicitly name the type of the FD being registered. If dma-fence/sync FD is the only type available in rev1, that's fine, but it's an easily extensible API.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>