add suggested local work size support for the command buffer emulation layer#163
Merged
add suggested local work size support for the command buffer emulation layer#163
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
As an optimization, we can get the suggested local work-group size for calls to clEnqueueNDRangeKernel during command buffer construction when the local work-group size is
NULLvs. determining the local work-group size each time clEnqueueNDRangeKernel is executed during command buffer execution. This isn't a huge improvement, but it reduces command buffer enqueue time by approximately 2% on some devices in submission microbenchmarks.