Google Git
Sign in
dawn / dawn / 86afbe086dfb75ebff1ca753e937f662a8a810d6
commit86afbe086dfb75ebff1ca753e937f662a8a810d6[log] [tgz]
authorAustin Eng <enga@chromium.org>Thu Feb 22 20:53:22 2024 +0000
committerDawn LUCI CQ <dawn-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu Feb 22 20:53:22 2024 +0000
tree41c9f7c31fa7a2285de6b7c71d41669f436779e1
parent53a0aae32a0ad1c67e8de6f98500504878473465 [diff]
remove global device lock for host-mapped-pointer buffers

This makes creation of these buffers thread-safe without
taking the global device lock. Note that destroying the
device while creating any resource is still not safe.

Tested on Linux with TSAN, that the implementation is
data-race free.

On d3d12, buffer creation:
 - uses the D3D12 device, which is thread-safe
 - uses the ResidencyManager which is MutexProtected
 - reads lots of device info/toggles; which are immutable
   after creation

On d3d12, buffer destruction
 - uses the deallocation queue which is MutexProtected
 - uses the callback task queue which is MutexProtected

On metal, buffer creation
 - uses the MTLDevice which is already thread-safe

On metal, buffer description
 - uses the callback task queue which is MutexProtected

On Vulkan, buffer creation
 - allocates with the VkDevice, which is thread-safe
 - reads lots of device state which is immutable after
   creation
 - uses the resource memory allocator which is MutexProtected

On vulkan, buffer destruction
 - uses the resource memory allocator which is MutexProtected
 - uses the fenced deleter which is MutexProtected
 - uses the callback task queue which is MutexProtected

Bug: dawn:1662
Change-Id: Ib0962a5f8afcc4b80a8f3d759d8ad80bf28c8094
Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/175208
Reviewed-by: Loko Kung <lokokung@google.com>
Kokoro: Kokoro <noreply+kokoro@google.com>
Reviewed-by: Corentin Wallez <cwallez@chromium.org>
Commit-Queue: Austin Eng <enga@chromium.org>
6 files changed
tree: 41c9f7c31fa7a2285de6b7c71d41669f436779e1
  1. .github/
  2. .vscode/
  3. build_overrides/
  4. docs/
  5. generator/
  6. include/
  7. infra/
  8. scripts/
  9. src/
  10. test/
  11. third_party/
  12. tools/
  13. webgpu-cts/
  14. build
  15. buildtools
  16. testing
  17. .bazelrc
  18. .clang-format
  19. .clang-tidy
  20. .gitattributes
  21. .gitignore
  22. .gitmodules
  23. .gn
  24. AUTHORS
  25. BUILD.bazel
  26. BUILD.gn
  27. CMakeLists.txt
  28. CMakeSettings.json
  29. CODE_OF_CONDUCT.md
  30. codereview.settings
  31. CONTRIBUTING.md
  32. CPPLINT.cfg
  33. DEPS
  34. DIR_METADATA
  35. go.mod
  36. go.sum
  37. go_presubmit_support.py
  38. LICENSE
  39. OWNERS
  40. PRESUBMIT.py
  41. README.chromium
  42. README.md
  43. WORKSPACE.bazel
README.md

Build Status Matrix Space

Dawn, a WebGPU implementation

Dawn is an open-source and cross-platform implementation of the WebGPU standard. More precisely it implements webgpu.h that is a one-to-one mapping with the WebGPU IDL. Dawn is meant to be integrated as part of a larger system and is the underlying implementation of WebGPU in Chromium.

Dawn provides several WebGPU building blocks:

  • WebGPU C/C++ headers that applications and other building blocks use.
    • The webgpu.h version that Dawn implements.
    • A C++ wrapper for the webgpu.h.
  • A “native” implementation of WebGPU using platforms' GPU APIs: D3D12, Metal, Vulkan and OpenGL. See per API support for more details.
  • A client-server implementation of WebGPU for applications that are in a sandbox without access to native drivers
  • Tint is a compiler for the WebGPU Shader Language (WGSL) that can be used in standalone to convert shaders from and to WGSL.

Helpful links:

Documentation table of content

Developer documentation:

User documentation: (TODO, figure out what overlaps with the webgpu.h docs)

License

BSD 3-Clause License, please see LICENSE.

Disclaimer

This is not an officially supported Google product.