Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cl_khr_command_buffer sync-point capacity #1286

Merged
merged 3 commits into from
Dec 12, 2024

Conversation

EwanC
Copy link
Contributor

@EwanC EwanC commented Nov 21, 2024

Document the behaviour when command-buffer command capacity is reached, and track under "Issues" the possible future use-cases for being able to optimize based on the capacity of a command-buffer.

Closes #844

Document the behaviour when command-buffer command capacity
is reached, and track under "Issues" the possible future
use-cases for being able to optimize based on the capacity
of a command-buffer.

Closes KhronosGroup#844
@EwanC EwanC added the cl_khr_command_buffer Relating to the command-buffer family of extension label Nov 21, 2024
api/cl_khr_command_buffer.asciidoc Outdated Show resolved Hide resolved
Copy link
Contributor

@kpet kpet left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@bashbaug bashbaug merged commit 91c4a0d into KhronosGroup:main Dec 12, 2024
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cl_khr_command_buffer Relating to the command-buffer family of extension
Projects
None yet
Development

Successfully merging this pull request may close these issues.

What happens on cl_sync_point_khr overflow?
3 participants