Add optimization barrier as no op #16439
Closed
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
For PGLE latency hiding scheduler, optimization barrier should be considered a no-op because it is never really executed.
mooskagh
approved these changes
Aug 26, 2024
copybara-service bot
pushed a commit
to tensorflow/tensorflow
that referenced
this pull request
Aug 26, 2024
Imported from GitHub PR openxla/xla#16439 For PGLE latency hiding scheduler, optimization barrier should be considered a no-op because it is never really executed. Copybara import of the project: -- 44bab12c6fb0b0c4d60ac62113eae7c959c05536 by Shraiysh Vaishay <svaishay@nvidia.com>: Add optimization barrier as no op For PGLE latency hiding scheduler, optimization barrier should be considered a no-op because it is never really executed. Merging this change closes #16439 FUTURE_COPYBARA_INTEGRATE_REVIEW=openxla/xla#16439 from shraiysh:fix_pgle_latency_scheduler 44bab12c6fb0b0c4d60ac62113eae7c959c05536 PiperOrigin-RevId: 667505975
copybara-service bot
pushed a commit
to tensorflow/tensorflow
that referenced
this pull request
Aug 26, 2024
Imported from openxla/triton#8 FUTURE_COPYBARA_INTEGRATE_REVIEW=openxla/xla#16439 from shraiysh:fix_pgle_latency_scheduler 44bab12c6fb0b0c4d60ac62113eae7c959c05536 PiperOrigin-RevId: 665336874
copybara-service bot
pushed a commit
to tensorflow/tensorflow
that referenced
this pull request
Aug 26, 2024
Imported from GitHub PR openxla/xla#16439 For PGLE latency hiding scheduler, optimization barrier should be considered a no-op because it is never really executed. Copybara import of the project: -- 44bab12c6fb0b0c4d60ac62113eae7c959c05536 by Shraiysh Vaishay <svaishay@nvidia.com>: Add optimization barrier as no op For PGLE latency hiding scheduler, optimization barrier should be considered a no-op because it is never really executed. Merging this change closes #16439 PiperOrigin-RevId: 667515007
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.
For PGLE latency hiding scheduler, optimization barrier should be considered a no-op because it is never really executed.