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.

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 cuDNN v5 support, drop cuDNN v3 support #4159

Merged
merged 3 commits into from
May 17, 2016

Conversation

flx42
Copy link
Contributor

@flx42 flx42 commented May 16, 2016

cuDNN v5 is now out, since PR #3919 is still being discussed, we need a solution to allow users to compile caffe with the new cuDNN version.
This PR is the bare minimum to enable cuDNN v5 with caffe while still being compatible with cuDNN v4 to give some time for users to transition to the newer version.
cuDNN v3 support is dropped to avoid further #ifdef hell.

Ping @longjon @shelhamer @ajtulloch

@thatguymike
Copy link
Contributor

Note that without the memory management changes and some of the commits to use it to enable more algorithms in cuDNN, performance is still far from Nvidia's caffe branch for most popular networks.

@shelhamer
Copy link
Member

Thanks for the minimal patch for compatibility @flx42! Thanks for noting the difference with further integration of the new algorithms in v5 @thatguymike.

With merge I will post the version change to the mailing list and publish the latest version of the Caffe site to incorporate the doc change.

We will turn to the full integration of cuDNN v5 after the NIPS deadline 05/20.

@Coderx7
Copy link
Contributor

Coderx7 commented Aug 20, 2016

what is the status of cudnn v5 now? Is it still WIP or is it finally dealt with like nvidia branch?

@shelhamer
Copy link
Member

Caffe has been cuDNN v5 compatible since this PR was merged. However, certain memory hungry convolution algorithms are more practical with CUB memory pool integration, which is still in progress.

@Jayhello
Copy link

I'm very sorry?
How to merge this to caffe?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants