forked from pytorch/pytorch
-
Notifications
You must be signed in to change notification settings - Fork 7
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
schedulePointwise cleanup: - computeAt + InlinePropagator #1815
Merged
Merged
Changes from all commits
Commits
Show all changes
23 commits
Select commit
Hold shift + click to select a range
3de1f1c
Use scheduler_utils to cache inputs and outputs in schedulePointwise
zasdfgbnm 586c0cd
save
zasdfgbnm 17a415c
Merge branch 'schedulepointwise-cleanup2' into pointwise-sched-no-ca
zasdfgbnm 153889a
save
zasdfgbnm fee489c
save
zasdfgbnm 9862162
save
zasdfgbnm 6284750
cleanup
zasdfgbnm 22a8cad
save
zasdfgbnm 3b39284
cleanup
zasdfgbnm dc176d5
more cleanup
zasdfgbnm 4301cb4
doc
zasdfgbnm 6ff9778
Merge branch 'devel' of github.com:csarofeen/pytorch into schedulepoi…
zasdfgbnm 73dfcd0
Merge branch 'schedulepointwise-cleanup2' into pointwise-sched-no-ca
zasdfgbnm be23523
fix merge error
zasdfgbnm f604d34
Merge branch 'schedulepointwise-cleanup2' into pointwise-sched-no-ca
zasdfgbnm 2517630
fix more merge error
zasdfgbnm d2fec0e
Merge branch 'schedulepointwise-cleanup2' into pointwise-sched-no-ca
zasdfgbnm 9bac081
Merge branch 'pointwise-sched-no-ca' of github.com:csarofeen/pytorch …
zasdfgbnm 5299efb
save
zasdfgbnm 72e4a4e
TORCH_CUDA_CU_API
zasdfgbnm 56b36d8
a new ctor for InlinePropagator
zasdfgbnm 0059dab
Merge branch 'devel' of github.com:csarofeen/pytorch into pointwise-s…
zasdfgbnm 24397fb
do not exclude cached_outputs
zasdfgbnm File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we call
MaxProducerPosUpdater
at the end ofInlinePropagator::traverse
?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
InlinePropagator
does not have atraverse
,MaxRootDomainInfoSpanningTree
does, so probably no?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Probably we should move the functionality of
MaxProducerPosUpdater
intoInlinePropagator::setCAPos
? I can do that in a separate PR, but doing so will slow down compilation speed as we will be updating the max producer pos of a tensor multiple times.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Or... Is the max producer position only used in expr sort? If so, we can just leave it as unset when scheduling, and add a pass in the lowering for setting it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Max producer position is important for multiple transformation passes. To make sure that we aren't modifying tensors that are being relied on by other tensors. It's more of a rule to enforce as we're modifying the schedule it remains legal.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think adding it to the tail end of inlining pass is worth the extra cost, as it will help catch user errors in scheduling.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agree it can be done in a separate PR.