Skip to content
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.

Sign up for GitHub

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

Adding comments #107

Merged
merged 3 commits into from
Aug 17, 2017
Merged

Adding comments #107

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
189d447
Remove unnecessary comment
iwiwi Aug 15, 2017
de0ff50
Describe why we don't use MPI4py's scatter
iwiwi Aug 15, 2017
9730427
Describe why we delay the communicator initialization
iwiwi Aug 15, 2017
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Describe why we delay the communicator initialization
  • Loading branch information
@iwiwi
iwiwi committed Aug 15, 2017
commit 9730427808401980d890846c5cca4cab567408ea
5 changes: 4 additions & 1 deletion chainermn/communicators/_base.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -96,7 +96,10 @@ def __init__(self, mpi_comm, use_nccl):

self._init_ranks()

# TODO(akiba): write why we delay initializing comms
# We have to delay the initialization of communicators. This is because
# NCCL's communicators use the current CUDA devices at the time of
# initialization. Therefore, we have to initialize NCCL communicators
# after users set the devices to use.
self.inter_mpi_comm = None
self.intra_mpi_comm = None
if self.use_nccl:
Expand Down