Native fence objects can be shared across process boundaries and allows Chromium to integrate more efficiently with Exosphere clients that are not using the GPU process for rendering.
Native fence primitives can also be used to improve CPU access to GpuMemoryBuffers as these primitives can be shared and accessed directly in a sandboxed renderer process, eliminating the need for polling and callbacks to improve performance, power and memory usage.
This same set of primitives can also be used for moving ChromeOS (Freon) away from implicit synchronization in favor explicit synchronization.
Comment 1 by bugdroid1@chromium.org
, Dec 18 2017