<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#c17">Comment # 17</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:tomek.bury@gmail.com" title="Tomek Bury <tomek.bury@gmail.com>"> <span class="fn">Tomek Bury</span></a>
</span></b>
<pre>(In reply to Daniel Stone from <a href="show_bug.cgi?id=97353#c16">comment #16</a>)
<span class="quote">> It doesn't give you standardised cross-process primitives, but EGL platforms
> and winsys mostly require working across process boundaries. </span >
Definitely not EGL:
"2.3 Direct Rendering and Address Spaces
EGL is assumed to support only direct rendering, unlike similar APIs such as
GLX. EGL objects and related context state cannot be used outside of the
address space in which they are created. In a single-threaded environment, each
process has its own address space. In a multi-threaded environment, all threads
may share the same virtual address space; however, this capability is not
required, and imple- mentations may choose to restrict their address space to
be per-thread even in an environment supporting multiple application threads.
Context state, including both the client and server state of OpenGL and OpenGL
ES contexts, exists in the client’s address space; this state cannot be shared
by a client in another process.
Support of indirect rendering (in those environments where this concept makes
sense) may have the effect of relaxing these limits on sharing. However, such
support is beyond the scope of this document."
<span class="quote">> It's entirely
> legitimate to place requirements on how they operate, without having to
> specify an entire generic mechanism for external fencing.</span >
I fully agree. Perhaps sync requirement should do here:
<a href="https://www.khronos.org/registry/egl/extensions/EXT/EGL_EXT_platform_wayland.txt">https://www.khronos.org/registry/egl/extensions/EXT/EGL_EXT_platform_wayland.txt</a>
<a href="https://www.khronos.org/registry/egl/extensions/KHR/EGL_KHR_platform_wayland.txt">https://www.khronos.org/registry/egl/extensions/KHR/EGL_KHR_platform_wayland.txt</a>
and here:
<a href="https://cgit.freedesktop.org/mesa/mesa/tree/docs/specs/WL_bind_wayland_display.spec">https://cgit.freedesktop.org/mesa/mesa/tree/docs/specs/WL_bind_wayland_display.spec</a>
(BTW. shouldn't this be submitted to Khronos?)</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>