1865984 - Add a capability of handling ID3D11Fence in WebGL

Status: NEW

(Core :: Graphics, task)

Description

[Sotaro Ikeda [:sotaro]]

It seems better to use ID3D11Fence with WebGL if it is supported. Since WebGPU needs to use ID3D11Fence.

Comment 1

[Sotaro Ikeda [:sotaro]]

Attachment: WIP: Bug 1865984 - Add ID3D11Fence handling to WebGL

Comment 2

[Jeff Muizelaar [:jrmuizel]]

What advantage does using ID3D11Fence provide?

Comment 3

[Sotaro Ikeda [:sotaro]]

If we want to implement GPUQueue:copyExternalImageToTexture(), HTMLCanvasElement and OffscreenCanvas could also be used as source.

• https://developer.mozilla.org/en-US/docs/Web/API/GPUQueue/copyExternalImageToTexture

In this case, ID3D11Texture2D of SharedSurface_ANGLEShareHandle is going to be imported to WebGPU(wgpu).
If we want to interact with WebGPU with D3D12 backend, SharedSurface_ANGLEShareHandle needs to provide ID3D11Fence for performance.

From it, all canvas that use ID3D11Texture2D will need to implement ID3D11Fence for performance.
And if WebGL support ID3D11Fence, we could check if ID3D11Fence implementation works as expected soon.

chromium implementation does like the following. The BeginAccessDawn() send wait fences to dawn(WebGPU)

GPUQueue::CopyFromCanvasSourceImage()
->WebGPUMailboxTexture::FromStaticBitmapImage()
->WebGPUMailboxTexture::FromCanvasResource()
->WebGPUMailboxTexture::WebGPUMailboxTexture()
->/// ipc
->WebGPUImplementation::AssociateMailbox()
->WebGPUDecoderImpl::HandleAssociateMailboxImmediate()
->WebGPUDecoderImpl::AssociateMailboxDawn()
->DawnImageRepresentation::BeginScopedAccess()
->DawnImageRepresentation::BeginAccess()
->DawnD3DImageRepresentation::BeginAccess()
->D3DImageBacking::BeginAccessDawn()