aboutsummaryrefslogtreecommitdiff
path: root/src/core/memory.cpp
diff options
context:
space:
mode:
authorReinUsesLisp <reinuseslisp@airmail.cc>2020-09-10 03:43:30 -0300
committerReinUsesLisp <reinuseslisp@airmail.cc>2020-09-19 01:46:37 -0300
commit7c747f9bead4a8c7feb9f0c2754dbe9159afb4f3 (patch)
tree9b7c3e28fa7445c78304902efe660356c59cad57 /src/core/memory.cpp
parent78267273ecf3384a9d92d839d8832b914717b718 (diff)
renderer_vulkan: Make unconditional use of VK_KHR_timeline_semaphore
This reworks how host<->device synchronization works on the Vulkan backend. Instead of "protecting" resources with a fence and signalling these as free when the fence is known to be signalled by the host GPU, use timeline semaphores. Vulkan timeline semaphores allow use to work on a subset of D3D12 fences. As far as we are concerned, timeline semaphores are a value set by the host or the device that can be waited by either of them. Taking advantange of this, we can have a monolithically increasing atomic value for each submission to the graphics queue. Instead of protecting resources with a fence, we simply store the current logical tick (the atomic value stored in CPU memory). When we want to know if a resource is free, it can be compared to the current GPU tick. This greatly simplifies resource management code and the free status of resources should have less false negatives. To workaround bugs in validation layers, when these are attached there's a thread waiting for timeline semaphores.
Diffstat (limited to 'src/core/memory.cpp')
0 files changed, 0 insertions, 0 deletions