Shader Execution Reordering #145
Open
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
This is a general purpose reordering trigger - it's not tied to any ray intersection operations
|
LGTM! |
|
(Thank you for your hard work, the implementation and description looks very polished.) |
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.
This PR adds support for Shader Execution Reordering (SER) in OptiX ray tracing calls (
jit_optix_ray_trace()). It also adds an explicit reodering function if the user wants to reorder threads based on a key that does not involve any ray intersection information:jit_optix_reorder.The SER functionality can be completely turned off with a new
ShaderExecutionReorderingJIT flag.No new tests were added. The triangle test was updated to correctly adopt the new ray tracing interface.