Skip to content
GitLab
Menu
Projects
Groups
Snippets
Loading...
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
Menu
Open sidebar
OpenDAS
fairscale
Commits
c06efdf6
Unverified
Commit
c06efdf6
authored
Mar 08, 2021
by
Myle Ott
Committed by
GitHub
Mar 08, 2021
Browse files
[fix] FSDP: fix CPU offload corner case (#496)
parent
ad611a34
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
6 additions
and
3 deletions
+6
-3
fairscale/nn/data_parallel/fully_sharded_data_parallel.py
fairscale/nn/data_parallel/fully_sharded_data_parallel.py
+6
-3
No files found.
fairscale/nn/data_parallel/fully_sharded_data_parallel.py
View file @
c06efdf6
...
...
@@ -967,14 +967,17 @@ class FullyShardedDataParallel(nn.Module):
# before the move_grads_to_cpu step so that this entire hook remains
# non-blocking. The downside is a bit more D2H transfer in that case.
if
self
.
mixed_precision
:
orig_param_grad_data
=
param
.
grad
.
data
param
.
grad
.
data
=
param
.
grad
.
data
.
to
(
dtype
=
param
.
data
.
dtype
)
# Don't let this memory get reused until after the transfer.
orig_param_grad_data
.
record_stream
(
torch
.
cuda
.
current_stream
())
# Optionally move gradients to CPU, typically used if one is running
# the optimizer on the CPU.
if
self
.
move_grads_to_cpu
:
param
.
_cpu_grad
.
copy_
(
param
.
grad
.
data
,
non_blocking
=
True
)
param
.
_cpu_grad
.
copy_
(
param
.
grad
.
data
,
non_blocking
=
False
)
# Don't let this memory get reused until after the transfer.
param
.
grad
.
data
.
record_stream
(
torch
.
cuda
.
current_stream
())
param
.
grad
.
data
=
param
.
_cpu_grad
# Don't let this memory get reused until after the transfers.
reduced_grad
.
record_stream
(
torch
.
cuda
.
current_stream
())
def
_queue_wait_for_post_backward
(
self
)
->
None
:
"""Try to queue a `wait_for_post_backward` callback.
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment