-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Add pageable/pinned tensor to cuda reliability note in pinmem tutorial #3261
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/tutorials/3261
Note: Links to docs will display an error until the docs builds have been completed. ✅ No FailuresAs of commit a019acb with merge base 13d365c ( This comment was automatically generated by Dr. CI and updates every 15 minutes. |
efb8e51
to
a707b7f
Compare
# However, in other cases we cannot make the same asusmption: when a tensor is placed in pinned memory, mutating the | ||
# original copy after calling the host-to-device transfer may corrupt the data received on GPU. | ||
# Similarly, when a transfer is achieved in the opposite direction, from GPU to CPU, or from any device that is not CPU | ||
# or GPU to any device that is not a CUDA-handled GPU (e.g., MPS), there is no guarantee that the data read on GPU is |
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.
# or GPU to any device that is not a CUDA-handled GPU (e.g., MPS), there is no guarantee that the data read on GPU is | |
# or GPU to any device that is not a CUDA-handled GPU (such as, MPS), there is no guarantee that the data read on GPU is |
4812b2a
to
b612d61
Compare
b612d61
to
a019acb
Compare
@svekars I corrected the spelling - should be good for final review |
Adds some more info on when it is unsafe to use
non_blocking
(namely with pinned tensors)cc @nairbv