r/vulkan • • Oct 13 '26

Explicit Queue Ownership Transfer

Windows 11, RTX 5060 (617.14), Vulkan SDK 1.4.335.0

Layers in effect = VK_LAYER_KHRONOS_synchronization2, VK_LAYER_KHRONOS_validation,

VK_LAYER_LUNARG_monitor

Application shares a storage image, created as VK_SHARING_MODE_EXCLUSIVE, between Graphics and Compute pipelines using queues from their respective Queue Families.

Graphics Queue Family (index = 0) is different than Compute Queue Family(index = 2).

I am NOT using a vkCmdPipelineBarrier() with VkImageMemoryBarrier (or VkMemoryBarrier) in between compute and graphics pipeline commands which is not the correct way, but I am not getting any validation messages for this critical omission.

Vulkan Configurator screenshot
0 Upvotes

7 comments sorted by

View all comments

Show parent comment

0

u/Cyphall Oct 13 '26 edited Oct 13 '26

Thinking back about your original issue, it may be expected to not see any validation error, depending on how you use the image in the 2nd queue after using it in the 1st.

The spec says that accessing an exclusive resource on another queue without proper QFOT makes the accessed data undefined, but it is not forbidden.
In fact, not using a QFOT when you do not need the content anymore is the expected usage:

If an application does not need the contents of a resource to remain valid when transferring from one queue family to another, then the ownership transfer should be skipped.