We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi Intel ideep team, thanks for the awesome works of integrating mkl-dnn with PyTorch.😃
I noticed that the pytorch_dnnl branch is used for such integration, while the latest commit shows the ideep leverages the 1.5 version of mkl-dnn.
pytorch_dnnl
1.5
$ cd /root/pytorch/third_party/ideep $ git log commit 938cc68897bb46b8d4b228966edd9e23e471cf3b (HEAD, origin/pytorch_dnnl) Author: pinzhenx <[email protected]> Date: Tue Jun 16 18:54:21 2020 +0000 bump onednn to v1.5
Our application runs PyTorch on Intel CPU architecture, and we relies on mkl-dnn to gain better performances.
We want to know when will ideep upgrades mkl-dnn for PyToch, do you have a timetable for doing so?
The text was updated successfully, but these errors were encountered:
We update oneDNN according to its release, after verifying and notifying PyTorch team.
Sorry, something went wrong.
No branches or pull requests
Hi Intel ideep team, thanks for the awesome works of integrating mkl-dnn with PyTorch.😃
I noticed that the
pytorch_dnnl
branch is used for such integration, while the latest commit shows the ideep leverages the1.5
version of mkl-dnn.Our application runs PyTorch on Intel CPU architecture, and we relies on mkl-dnn to gain better performances.
We want to know when will ideep upgrades mkl-dnn for PyToch, do you have a timetable for doing so?
The text was updated successfully, but these errors were encountered: