Fix MTL completion fences discarded by newer CBs #39
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
For future reference, see this discord message. |
|
Just gonna post it here for those without Discord: "The GPU starts the command buffer after it starts any command buffers that are ahead of it in the same command queue". "All command buffers sent to a single queue are guaranteed to execute in the order in which the command buffers were enqueued." Links to the above guide programming guide, but again mentions "execution". I could be wrong. I believe order of execution is important for one and only one reason - to prevent deadlocks, because you can waitForFence: from a CB. |
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Command buffers execution is started in order, but is not guaranteed to complete in order.