<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Wayland lacks cross-process synchronisation"
href="https://bugs.freedesktop.org/show_bug.cgi?id=97353#c4">Comment # 4</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Wayland lacks cross-process synchronisation"
href="https://bugs.freedesktop.org/show_bug.cgi?id=97353">bug 97353</a>
from <span class="vcard"><a class="email" href="mailto:krh@bitplanet.net" title="Kristian Høgsberg <krh@bitplanet.net>"> <span class="fn">Kristian Høgsberg</span></a>
</span></b>
<pre>(In reply to Tomek Bury from <a href="show_bug.cgi?id=97353#c2">comment #2</a>)
<span class="quote">> As far as I can tell several 3D drivers put read-write synchronisation in
> user space so it works across contexts within one process but not across
> processes. Nokia had this problem, Boroadcom driver is another example.
>
> It's not impossible to implement but the only possible implementation that
> doesn't involve blocking CPU in the compositor I can think of is rather
> ugly: create a parallel synchronisation mechanism and deal with 2 of them:
> regular one in user pace for most things and Wayland special in kernel with
> an extra kernel round-trip for each read from or write to wl_buffer.</span >
The wl_drm interface isn't supposed to be the only buffer sharing interface.
Similiar to how drivers can define their own buffer sharing mechanism for X, a
driver can implement its own wayland interface for sharing buffers.
For driver architectures that require userspace synchronization, you would
define your own buffer sharing interface and pass along fences for each shared
buffer.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>