Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Don't store device indices separately on FutureNCCL (#48501)
Summary: Pull Request resolved: #48501 This commit is part of a stack that reworks FutureNCCL in order to extract a generic CUDA-aware Future subclass. The stack deliberately breaks up this transition into elementary changes, to make it easier to verify that the behavior is preserved (or to highlight how it gets changed). --- FutureNCCL stores a set of devices (on which the tensors in the data reside) and a CUDA event for each of those devices. In fact, each event instance also already contains the device it belongs to, which means we can avoid storing that information separately (with the risk that it'll be mismatched and/or inaccurate). ghstack-source-id: 118180024 Test Plan: Unit tests Reviewed By: mrshenli Differential Revision: D25177554 fbshipit-source-id: 64667c176efc2a7dafe99457a1fbba5d142cb06c
- Loading branch information
1 parent
e294c2d
commit 9fe3ac3
Showing
2 changed files
with
18 additions
and
41 deletions.
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