KhronosGroup / KhronosGroup/Vulkan-Docs
External synchronization on command buffer reset
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 3.3k
- Forks
- 549
- Avg merge
- 5d 5h
- Merged PRs (30d)
- 2
Description
The specification states in the 'Threading Behavior' section:
In addition, there are some implicit parameters that need to be externally synchronized. For
example, all commandBuffer parameters that need to be externally synchronized imply that the
commandPool that was passed in when creating that command buffer also needs to be externally
synchronized.
The following list of implicitly synchronized parameters doesn't contain the pool when reseting command buffers via vkResetCommandBuffer even though the commandBuffer parameter there needs to be externally synchronized.
Is this an oversight or intentional as the text implies it would also include this function.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the specification's “Threading Behavior” section and the implicit-synchronization list for vkResetCommandBuffer. Check how the commandBuffer parameter is described there and determine whether the command pool should be listed as implicitly synchronized. Done means the specification consistently documents the intended synchronization behavior.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100