Vulkan: Resource Submission Tracking #105183

In Vulkan multiple commands can be in flight simultaneously.

These commands can share resources like descriptor sets or push
constants. When between commands these resources are updated
a new version of the resources should be created.

When a resource is updated it should check the submission id of the
command buffer. If this is different than last known by the resources,
the previous resources should be freed.
If the submission id is the same than previously it has to create a
new version of the resource to not intervene with other commands that
uses the resource before the update.
When the resource wasn't updated between multiple usages in the same
submission id it could reuse the previous resource.

This PR introduces a ResourceTracker and a SubmissionTracker.
A submission tracker can check if the command buffer is submitted.
In this case all resources of the resource tracker should be freed.
Unmodified resources in the same submission can be shared.

A resource tracker will keep track of all resources that are in
flight. After the resources are used (submission + execution) have
finished the resources can be cleared.

Related issue #104771

In Vulkan multiple commands can be in flight simultaneously. These commands can share resources like descriptor sets or push constants. When between commands these resources are updated a new version of the resources should be created. When a resource is updated it should check the submission id of the command buffer. If this is different than last known by the resources, the previous resources should be freed. If the submission id is the same than previously it has to create a new version of the resource to not intervene with other commands that uses the resource before the update. When the resource wasn't updated between multiple usages in the same submission id it could reuse the previous resource. This PR introduces a `ResourceTracker` and a `SubmissionTracker`. A submission tracker can check if the command buffer is submitted. In this case all resources of the resource tracker should be freed. Unmodified resources in the same submission can be shared. A resource tracker will keep track of all resources that are in flight. After the resources are used (submission + execution) have finished the resources can be cleared. Related issue #104771

I am not sure I am understanding the whole concept. It might be easier to do an in-person explanation so I can give a better appreciation.

So for the time being I'll only review the code quality. Only a small comment about naming but looks fine otherwise.

I am not sure I am understanding the whole concept. It might be easier to do an in-person explanation so I can give a better appreciation. So for the time being I'll only review the code quality. Only a small comment about naming but looks fine otherwise.

 @ -119,2 +124,3 @@
   {
     GPU_compute_dispatch(shader, 1, 1, 1);
     /* Dispatching 1000000 times to add some stress to the GPU. Without it tests may succeed when
      * using to simple shaders. */

 @ -0,0 +24,4 @@
  * a new version of these resources should be created.
  *
  * When a resource is updated it should check the submission id of the
  * command buffer. If this is different than resources can be reused.

 @ -0,0 +32,4 @@
  * SubmissionID is the identifier to keep track if a new submission is
  * being recorded.
  */
 struct SubmissionID {

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Vulkan: Resource Submission Tracking #105183

Reviewers