[go: nahoru, domu]

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}
24 files changed
tree: fb635bd30fd2a108e6778248f74ca22c1e454d8f
  1. android_webview/
  2. apps/
  3. ash/
  4. base/
  5. build/
  6. build_overrides/
  7. buildtools/
  8. cc/
  9. chrome/
  10. chromecast/
  11. chromeos/
  12. codelabs/
  13. components/
  14. content/
  15. courgette/
  16. crypto/
  17. dbus/
  18. device/
  19. docs/
  20. extensions/
  21. fuchsia_web/
  22. gin/
  23. google_apis/
  24. google_update/
  25. gpu/
  26. headless/
  27. infra/
  28. ios/
  29. ipc/
  30. media/
  31. mojo/
  32. native_client_sdk/
  33. net/
  34. pdf/
  35. ppapi/
  36. printing/
  37. remoting/
  38. rlz/
  39. sandbox/
  40. services/
  41. skia/
  42. sql/
  43. storage/
  44. styleguide/
  45. testing/
  46. third_party/
  47. tools/
  48. ui/
  49. url/
  50. weblayer/
  51. .clang-format
  52. .clang-tidy
  53. .eslintrc.js
  54. .git-blame-ignore-revs
  55. .gitattributes
  56. .gitignore
  57. .gn
  58. .mailmap
  59. .rustfmt.toml
  60. .vpython3
  61. .yapfignore
  62. ATL_OWNERS
  63. AUTHORS
  64. BUILD.gn
  65. CODE_OF_CONDUCT.md
  66. codereview.settings
  67. DEPS
  68. DIR_METADATA
  69. LICENSE
  70. LICENSE.chromium_os
  71. OWNERS
  72. PRESUBMIT.py
  73. PRESUBMIT_test.py
  74. PRESUBMIT_test_mocks.py
  75. README.md
  76. WATCHLISTS
README.md

Logo Chromium

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.