You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 17, 2023. It is now read-only.
This is Jin from Intel MXNet Shanghai team, we spent some time analyzing current MXNet make/cmake flow, especially the part related with MKLDNN and BLAS selection and full MKL/MKLML library link usage/dependency. We came out with a small summary slides mainly talk about below items:
(1) MKLDNN, full MKL, MKLML library relationship
(2) BLAS selection
(3) Our preferred MXNet Build Logic regarding full MKL/MKLML library
(4) Current build logic, issues, and potential improvements
Please help to take at the slides and we can discuss for further comments. Thanks.
The text was updated successfully, but these errors were encountered:
As a follow-up #10075, @jinhuang415 makes up this slide and I think we need to figure out a clear and efficient flow for MKL-DNN related building issue.
Hi MXNet owners,
This is Jin from Intel MXNet Shanghai team, we spent some time analyzing current MXNet make/cmake flow, especially the part related with MKLDNN and BLAS selection and full MKL/MKLML library link usage/dependency. We came out with a small summary slides mainly talk about below items:
(1) MKLDNN, full MKL, MKLML library relationship
(2) BLAS selection
(3) Our preferred MXNet Build Logic regarding full MKL/MKLML library
(4) Current build logic, issues, and potential improvements
Please help to take at the slides and we can discuss for further comments. Thanks.
The text was updated successfully, but these errors were encountered: