tree 8cbc6f6a5fc8ce1cd2856b406612b90d0357be23
parent f87b62a9044204a76c286ba6984b63716eaa1c87
author Yunchao He <yunchao.he@intel.com> 1591981301 +0000
committer Commit Bot service account <commit-bot@chromium.org> 1591981301 +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 <cwallez@chromium.org>
Reviewed-by: Austin Eng <enga@chromium.org>
Commit-Queue: Yunchao He <yunchao.he@intel.com>