Caching look up table (LUT) in work-group local memory #4
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
Signed-off-by: Anjan Roy <[email protected]>
… Iris Max GPU Code checked out at commit 2271291 Signed-off-by: Anjan Roy <[email protected]>
…commit 32c9f06 Signed-off-by: Anjan Roy <[email protected]>
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.
Harpocrates SYCL kernels can now process input
because often accessed (inverse) look up table (LUT) is first explicitly cached in work-group local memory, which makes it cheaper to access for all work-items of certain work-group. Work-group leader takes up the responsibility of explicitly copying look up table ( of 256 -bytes ) to faster work-group local memory & until that operation is finished all other work-items wait for work-group leader.