I'm confused with the three: MKL MKLML MKLDNN?
Is there a runtime dependency in the three?
MKL is a full library, containing all the functionality. It is free under community support licensing (https://software.intel.com/en-us/articles/free-mkl).
MKLML is a subset of MKL and it's built by the MKL release team using standard MKL custom dynamic library builder. It contains smaller number of functions to reduce the size of the download and reduce the number of dynamic libraries user needs.
MKLDNN is a separate open-source library actually developed by one of the MKL teams and that can be built completely standalone. But it does support linking with MKLML or full MKL for additional performance.
Hope this helps. Feel free to ask any further questions.
many thanks
@rsdubtso The great explanation! Is it possible to add it into README page?
@rsdubtso, are there any other changes since MKLDNN is rebranding into DNNL?
Hi @bobuntu,
The new name of the project is oneDNN. In addition to this starting from v1.0 the library has fully performant implementation of GEMM functionality and does not support linking to Intel MKL (or MKLML). We also stopped distributing MKLML package.
Most helpful comment
MKL is a full library, containing all the functionality. It is free under community support licensing (https://software.intel.com/en-us/articles/free-mkl).
MKLML is a subset of MKL and it's built by the MKL release team using standard MKL custom dynamic library builder. It contains smaller number of functions to reduce the size of the download and reduce the number of dynamic libraries user needs.
MKLDNN is a separate open-source library actually developed by one of the MKL teams and that can be built completely standalone. But it does support linking with MKLML or full MKL for additional performance.
Hope this helps. Feel free to ask any further questions.