Present WebGPU without readback on Windows
Categories
(Core :: Graphics: WebGPU, enhancement)
Tracking
()
Tracking | Status | |
---|---|---|
firefox126 | --- | fixed |
People
(Reporter: sotaro, Assigned: sotaro)
References
(Depends on 2 open bugs, Blocks 2 open bugs)
Details
Attachments
(6 files, 5 obsolete files)
For now, gecko does readback to present WebGPU on all platforms. It is not good.
On Windows, we expected to use DX12 by default.
Since Bug 1805209 fix, WebGPU present uses RemoteTexture.
Assignee | ||
Updated•1 year ago
|
Assignee | ||
Updated•1 year ago
|
Assignee | ||
Comment 1•1 year ago
|
||
From chromium's implementation, it seems possible interoperate between ID3D11Texture2D and DX12. It is implemented around D3DImageBacking.
Assignee | ||
Comment 2•1 year ago
|
||
Assignee | ||
Comment 3•1 year ago
|
||
On gecko, one webgpu::Texture is reused in CanvasContext::GetCurrentTexture(). It seems better to use different Texture when Texture is posted to WebRender.
On chromium, WebGPUSwapBufferProvider manages SharedImage allocation and recycling.
Assignee | ||
Updated•1 year ago
|
Assignee | ||
Comment 4•1 year ago
|
||
Assignee | ||
Comment 5•1 year ago
|
||
It is just current rough idea. It should be changed with more investigations.
Comment 6•11 months ago
|
||
:sotaro: What is the relation of this bug's scope to bug 1708025? I see mention of readback there, but I'm unclear if that's tangential or not.
CC :jimb, :jgilbert.
Assignee | ||
Comment 7•11 months ago
|
||
bug 1708025 just mentioned about RenderD3D11TextureHost. Then it could be dup of this bug.
Assignee | ||
Updated•11 months ago
|
Assignee | ||
Comment 9•11 months ago
|
||
Assignee | ||
Comment 10•11 months ago
|
||
Assignee | ||
Updated•11 months ago
|
Assignee | ||
Updated•11 months ago
|
Assignee | ||
Updated•11 months ago
|
Assignee | ||
Comment 11•11 months ago
|
||
Assignee | ||
Updated•11 months ago
|
Comment 12•11 months ago
|
||
This bug appears to be receiving active effort from Sotaro. :sotaro, is the intent to resolve this bug fully within the next release or so? I'm assuming so, but I wanted to double-check.
Tentatively marking as P1 to indicate this, but feel free to correct.
Assignee | ||
Comment 13•11 months ago
|
||
early stage of implementation.
Comment 14•10 months ago
|
||
Yes, Sotaro is working on this, and we're expecting it to be done within 2023H2, but we don't have a specific release as an ETA.
Comment 15•10 months ago
|
||
P1 seems appropriate.
Assignee | ||
Comment 16•9 months ago
|
||
Updated•9 months ago
|
Assignee | ||
Updated•9 months ago
|
Assignee | ||
Comment 17•8 months ago
|
||
Assignee | ||
Comment 18•8 months ago
|
||
Assignee | ||
Comment 19•8 months ago
|
||
Updated•3 months ago
|
Comment 20•3 months ago
|
||
Pushed by sikeda.birchill@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/122147bb13ec Enable to present WebGPU without readback with DX12 on Windows r=webgpu-reviewers,nical
Comment 21•3 months ago
|
||
bugherder |
Description
•