| commit | d199409f6411a7e96d4649f73f7e2b9ece378dfc | [log] [tgz] |
|---|---|---|
| author | Bryan Bernhart <bryan.bernhart@intel.com> | Wed May 07 19:39:23 2025 |
| committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed May 07 19:39:23 2025 |
| tree | dcc7d6666425388741d75518ccee61857dbc313d | |
| parent | 0e29ab4b1eddf18365ba5c4b41bce0a8c7a00e34 [diff] |
WebNN: Implement begin/end access in DML backend Allows `TensorImplDml` instances to be used by the GPU service through a backend-specific interface which implements BeginAccess and EndAccess to sync contents with another GPU command queue. Upon end access, WebNN outputs its submission fence which another queue waits for WebNN to signal. Once WebNN's wait has completed, GPU work using this tensor from another queue can occur. To begin access, a fence is provided as input for WebNN to wait on which another queue signals upon completion. Tensors are created by default with begin access. Once access ends, the tensor is unusable in WebNN context operations to ensure no data hazard between queues. Once access begin, WebNN resumes use of the tensor by the context. This change does not touch the renderer: it is entirely within the WebNN service. Bug: 345352987 Change-Id: I612eefaabb7aa608485c21a4ecf2ff370c7faeec Cq-Include-Trybots: luci.chromium.try:win11-blink-rel Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5621864 Reviewed-by: ningxin hu <ningxin.hu@intel.com> Commit-Queue: Bryan Bernhart <bryan.bernhart@intel.com> Reviewed-by: Rafael Cintron <rafael.cintron@microsoft.com> Cr-Commit-Position: refs/heads/main@{#1457202}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure.
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.