我是否需要在下一次转移时将所有权*转移回转移队列

我计划使用其中一个vulkan同步示例作为如何处理不频繁更新的统一缓冲区的参考。具体来说，我看到了这个：

vkBeginCommandBuffer(...);
// Submission guarantees the host write being complete, as per
// https://www.khronos.org/registry/vulkan/specs/1.0/html/vkspec.html#synchronization-submission-host-writes
// So no need for a barrier before the transfer
// Copy the staging buffer contents to the vertex buffer
VkBufferCopy vertexCopyRegion = {
.srcOffset = stagingMemoryOffset,
.dstOffset = vertexMemoryOffset,
.size      = vertexDataSize};
vkCmdCopyBuffer(
commandBuffer,
stagingBuffer,
vertexBuffer,
1,
&vertexCopyRegion);

// If the graphics queue and transfer queue are the same queue
if (isUnifiedGraphicsAndTransferQueue)
{
// If there is a semaphore signal + wait between this being submitted and
// the vertex buffer being used, then skip this pipeline barrier.
// Pipeline barrier before using the vertex data
// Note that this can apply to all buffers uploaded in the same way, so
// ideally batch all copies before this.
VkMemoryBarrier memoryBarrier = {
...
.srcAccessMask = VK_ACCESS_TRANSFER_WRITE_BIT,                           
.dstAccessMask = VK_ACCESS_VERTEX_ATTRIBUTE_READ_BIT};
vkCmdPipelineBarrier(
...
VK_PIPELINE_STAGE_TRANSFER_BIT ,      // srcStageMask
VK_PIPELINE_STAGE_VERTEX_INPUT_BIT,   // dstStageMask
1,                                    // memoryBarrierCount
&memoryBarrier,                       // pMemoryBarriers
...);

vkEndCommandBuffer(...);
vkQueueSubmit(unifiedQueue, ...);
}
else
{
// Pipeline barrier to start a queue ownership transfer after the copy
VkBufferMemoryBarrier bufferMemoryBarrier = {
...
.srcAccessMask = VK_ACCESS_TRANSFER_WRITE_BIT,                           
.dstAccessMask = 0,
.srcQueueFamilyIndex = transferQueueFamilyIndex,
.dstQueueFamilyIndex = graphicsQueueFamilyIndex,
.buffer = vertexBuffer,
...};
vkCmdPipelineBarrier(
...
VK_PIPELINE_STAGE_TRANSFER_BIT ,      // srcStageMask
VK_PIPELINE_STAGE_BOTTOM_OF_PIPE_BIT, // dstStageMask
1,                                    // bufferMemoryBarrierCount
&bufferMemoryBarrier,                 // pBufferMemoryBarriers
...);

vkEndCommandBuffer(...);
// Ensure a semaphore is signalled here which will be waited on by the graphics queue.
vkQueueSubmit(transferQueue, ...);
// Record a command buffer for the graphics queue.
vkBeginCommandBuffer(...);
// Pipeline barrier before using the vertex buffer, after finalising the ownership transfer
VkBufferMemoryBarrier bufferMemoryBarrier = {
...
.srcAccessMask = 0,                           
.dstAccessMask = VK_ACCESS_VERTEX_ATTRIBUTE_READ_BIT,
.srcQueueFamilyIndex = transferQueueFamilyIndex,
.dstQueueFamilyIndex = graphicsQueueFamilyIndex,
.buffer = vertexBuffer,
...};
vkCmdPipelineBarrier(
...
VK_PIPELINE_STAGE_TOP_OF_PIPE_BIT,    // srcStageMask
VK_PIPELINE_STAGE_VERTEX_INPUT_BIT,   // dstStageMask
...
1,                                    // bufferMemoryBarrierCount
&bufferMemoryBarrier,                 // pBufferMemoryBarriers
...);

vkEndCommandBuffer(...);
vkQueueSubmit(graphicsQueue, ...);
}

在这个例子中，我将其简化为：

map updated buffer which is host coherent
perform transfer in transfer queue to device local memory
make sure to put a buffer memory barrier to handle the queue ownership transfer
perform normal draw commands
make sure to put a buffer memory barrier to handle receiving of buffer in queue ownership

然后我是否必须恢复传输队列再次复制该数据的能力？似乎没有一个例子提到它，但我可能错过了它。我真的看不出添加另一个缓冲区屏障对同一个draw命令缓冲区会如何工作，因为即使我没有任何东西要传输，它也会在下一次提交时停滞，所以在提交下一次传输操作之前，我只需要提交另一个命令缓冲区来进行队列所有权传输吗？

即

//begin with transfer ownership
submit(copy)
submit(ownership to graphics)
submit(draw)
submit(ownership to transfer)
submit(copy)
submit(ownership to graphics)
submit(draw)
submit(draw)
submit(draw)
submit(ownership to transfer)
submit(copy)
submit(ownership to graphics)
submit(draw)

如果是这样的话，我不确定如何处理draw和transfer以及copy和draw之间的信号量信号。一开始这很容易，但后来因为多个帧而变得奇怪，因为绘制提交之间没有依赖关系。基本上，我想我需要设置我提交的最新绘图命令，以便有一个信号量来表示所有权的转移，这将表示副本，这将表明图形的所有权，如果它在一个单独的线程上，我将检查这个副本是否已提交，并且需要等待图形传输的所有权并重新设置提交副本的检查。但我不确定下一帧会发生什么，因为下一帧没有这种依赖性，并且可能在上一帧之前完成？