-
Notifications
You must be signed in to change notification settings - Fork 26.3k
[9/N] [Dispatchable Collectives] Update reduce_scatter with CPU / CUDA implementations #86166
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
Conversation
…A implementations [ghstack-poisoned]
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/86166
Note: Links to docs will display an error until the docs builds have been completed. ⏳ No Failures, 6 PendingAs of commit 569b2f7: This comment was automatically generated by Dr. CI and updates every 15 minutes. |
|
/easycla As part of the transition to the PyTorch Foundation, this project now requires contributions be covered under the new CLA. See #85559 for additional details. This comment will trigger a new check of this PR. If you are already covered, you will simply see a new "EasyCLA" check that passes. If you are not covered, a bot will leave a new comment with a link to sign. |
…h CPU / CUDA implementations" ### Changes - Updates for the reduce_scatter collective ### Context #86225 [ghstack-poisoned]
|
@H-Huang has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator. |
…h CPU / CUDA implementations" ### Changes - Updates for the reduce_scatter collective ### Context #86225 Differential Revision: [D40145699](https://our.internmc.facebook.com/intern/diff/D40145699) [ghstack-poisoned]
| if collective == dist.all_gather: | ||
| collective([tensor], tensor, *args) | ||
| elif collective == dist.reduce_scatter: | ||
| if backend != "gloo": |
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.
with the dispatchable functionality, what would happen if user call reduce_scatter on CPU?
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.
Sorry, I missed this question. It will call the reduce_scatter based on the configured backend for CPU (we will set a backend for CPU by default, but users can configure this). This is yet to be implemented in this PR
…h CPU / CUDA implementations" ### Changes - Updates for the reduce_scatter collective ### Context #86225 Differential Revision: [D40145699](https://our.internmc.facebook.com/intern/diff/D40145699) [ghstack-poisoned]
|
@H-Huang has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator. |
kwen2501
left a comment
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.
LGTM.
…h CPU / CUDA implementations" ### Changes - Updates for the reduce_scatter collective ### Context #86225 [ghstack-poisoned]
|
@pytorchbot merge |
Merge startedYour change will be merged once all checks pass (ETA 0-4 Hours). Learn more about merging in the wiki. Questions? Feedback? Please reach out to the PyTorch DevX Team |
…A implementations (pytorch#86166) ### Changes - Updates for the reduce_scatter collective ### Context pytorch#86225 Pull Request resolved: pytorch#86166 Approved by: https://github.com/kwen2501
…A implementations (pytorch#86166) ### Changes - Updates for the reduce_scatter collective ### Context pytorch#86225 Pull Request resolved: pytorch#86166 Approved by: https://github.com/kwen2501
Stack from ghstack:
Changes
Context
#86225