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
Allow override of backend in dist.new_group() #18595
Conversation
8099a75
to
e09f7c9
Compare
e09f7c9
to
5285c2e
Compare
5285c2e
to
ca1e549
Compare
ca1e549
to
514873d
Compare
514873d
to
55f1ef1
Compare
55f1ef1
to
e42260a
Compare
e42260a
to
dcb8d58
Compare
dcb8d58
to
b1beb4b
Compare
Checks if the Gloo backend is available. | ||
|
||
""" | ||
return True |
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.
This seems wrong? IIRC you can build PyTorch without gloo, so we should have a check for that
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.
@apaszke Updated Added docstring for new |
b1beb4b
to
d1984db
Compare
Summary: Pull Request resolved: pytorch#18595 There is no need to force the backend to be the same as the global process group, as long as the backend is "nccl" or "gloo". Reviewed By: mrshenli Differential Revision: D14657204 fbshipit-source-id: d8764874e8cfc5306c00e1ca9a951ae88edb7875
d1984db
to
524f92e
Compare
524f92e
to
0312889
Compare
This pull request has been merged in 7a19d3c. |
Is there any demonstration of the usage of new_group()? |
Summary:
There is no need to force the backend to be the same as the global
process group, as long as the backend is "nccl" or "gloo".
Differential Revision: D14657204