Open
Bug 1141730
Opened 9 years ago
Updated 2 years ago
The shared surface (Producer|Consumer)(Acquire|Release) API doesn't forces bad performance when implemented on fences
Categories
(Core :: Graphics: CanvasWebGL, enhancement, P5)
Core
Graphics: CanvasWebGL
Tracking
()
NEW
People
(Reporter: jrmuizel, Unassigned)
Details
(Whiteboard: [webgl-perf][gfx-noted])
(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.
|
||
Updated•9 years ago
|
OS: Mac OS X → All
Hardware: x86 → All
Whiteboard: webgl-perf
|
||
Updated•9 years ago
|
Whiteboard: webgl-perf → [webgl-perf][gfx-noted]
|
|
||
Updated•5 years ago
|
Type: defect → enhancement
Priority: -- → P5
|
||
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•