Correct tensor copy misuse #10412
Merged
Correct tensor copy misuse #10412
Conversation
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
chengduoZH
reviewed
May 7, 2018
There was a problem hiding this comment.
If we replace cudaMalloc with cudaMallocHost, the memory::Copy should have sync and async operation respectively, because someplace call memory::Copy directly. For example
Paddle/paddle/fluid/framework/tensor_util.h
Lines 104 to 105 in 99acf1d
|
In current design, |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Correct misusing of
TensorCopyin following ops or op tests:concat_test
sequence_padding_test
multiplex_op
sequence_slice_op
lod_reset_op