commit | c8a5ff63b1526ff9af3df49c8fd16d8ba054a060 | [log] [tgz] |
---|---|---|
author | Ningxin Hu <ningxin.hu@intel.com> | Fri Aug 04 03:53:28 2023 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Aug 04 03:53:28 2023 |
tree | fb635bd30fd2a108e6778248f74ca22c1e454d8f | |
parent | 8c9cc5bc61bda093464b678869b779162459734f [diff] |
WebNN: Share the Adapter with multiple contexts on the same adapter This CL addresses a TODO of CL-4647885 [1] that recommends multiple contexts should share one command queue when they are on the same adapter for better concurrency. To implement this optimization, this CL moves the `dml::Adapter::Create()` method to private and adds `dml::Adapter::GetInstance()` method which only creates a new instance if the instance doesn’t exist for a physical adapter. `WebNNContextProviderImpl` would call `dml::Adapter::GetInstance()` when creating a context. `dml::ContextImpl` is introduced to keep a reference to the `dml::Adapter` instance and pass the queue and device to `dml::GraphImpl` when creating the graph. The `Adapter` instance is shared and reference-counted by all `dml::ContextImpl` and it is released when all references are destroyed. At the current stage, only the default `Adapter` for the adapter queried from ANGLE is supported. In the future, the `Adapter` instance will be created based on context options. [1]: https://chromium-review.googlesource.com/c/chromium/src/+/4647885/comment/b24ff17b_69849b90/ Bug: 1273291 Change-Id: I8acf4af3ef23f514c83c34b84368eb9f4bf4de73 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4733931 Reviewed-by: Rafael Cintron <rafael.cintron@microsoft.com> Commit-Queue: ningxin hu <ningxin.hu@intel.com> Cr-Commit-Position: refs/heads/main@{#1179421}
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.