Closed
Conversation
Member
|
Should we upstream this to |
Author
|
We should do this when we push cub. This accomplishes something similar to what I did inside the cudnn paths. It alternatively fixes potential allocation failures, but does it always as opposed to when required. I don't think the reshape is needed for usual paths, it's pretty cuDNN specific. I want to understand the tradeoffs before we merge into Caffe-0.14 or BVLC/caffe |
Member
|
Closed as per @thatguymike's feedback. We've fixed this in another way. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Port #35 to caffe-0.14. Hold for more testing and validation.