The shared surface (Producer|Consumer)(Acquire|Release) API doesn't forces bad performance when implemented on fences

NEW
Unassigned

Status

()

Core
Canvas: WebGL
3 years ago
3 years ago

People

(Reporter: jrmuizel, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [webgl-perf][gfx-noted])

(Reporter)

Description

3 years ago
(Producer|Consumer)(Acquire|Release) requires holding the lock as long as you're reading or writing to a surface. Fences let you specify exactly which state you want to be consumed on the other side. It would be nice if we had an API that allowed for both of these things.

Bug 1136242 contains an example of where this difference makes a difference.
OS: Mac OS X → All
Hardware: x86 → All
Whiteboard: webgl-perf

Updated

3 years ago
Whiteboard: webgl-perf → [webgl-perf][gfx-noted]
You need to log in before you can comment on or make changes to this bug.