You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
// This semaphore is needed to "stitch together" additional submits, ensuring they occur before and after the original intended signals and waits.
95
-
// It also ensures safe usage of the scratch command buffers by blocking the CPU if the command buffer is in a PENDING state and not safe to begin.
94
+
// This semaphore is needed to indicate when each sub-submit is complete and resources can be reclaimed.
95
+
// It also ensures safe usage of the scratch command buffers by blocking the CPU if the next scratch command buffer to use is in a PENDING state and not safe to begin.
96
96
// The initial `scratchSemaphore.value` gets incremented and signaled on each submit. It can start at 0 because an overflow will signal `value+1`.
97
97
// NOTE: You should signal this semaphore when doing your last/tail submit manually OR when not submitting the recorded scratch at all
98
98
// (in which case, signal from Host or another submit). Why? The utilities that deal with `SIntendedSubmitInfo` might use the
0 commit comments