|author||Yunchao He <firstname.lastname@example.org>||Fri Jun 12 17:01:41 2020 +0000|
|committer||Commit Bot service account <email@example.com>||Fri Jun 12 17:01:41 2020 +0000|
Vulkan: use one barrier if we can for non-pass operations When we do transition barriers for a texture view outside of a pass (say copy, clear, initialization), if the texture view can cover all subresources, and its old usages across all subresources are the same, then we can use one transition barrier. We don't need to use separate barrier per each subresource. This patch can reduce barrier we delivered, and improve performance for particular situations. Bug: dawn:441 Change-Id: I2ae9b39793915553cbaaceacaf58bf87c9ba3bc6 Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/23129 Reviewed-by: Corentin Wallez <firstname.lastname@example.org> Reviewed-by: Austin Eng <email@example.com> Commit-Queue: Yunchao He <firstname.lastname@example.org>
Dawn is an open-source and cross-platform implementation of the work-in-progress 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.hversion that Dawn implements.
User documentation: (TODO, figure out what overlaps with webgpu.h docs)
Apache 2.0 Public License, please see LICENSE.
This is not an officially supported Google product.