TaoLv commented on issue #14335: [MKLDNN] Question on installation and use of
MKLDNN
URL:
https://github.com/apache/incubator-mxnet/issues/14335#issuecomment-471408977
@dbsxdbsx could you post the steps for reproducing the build issue? Or
typical steps for building mxnet from a Windows user perspective. I also sent
an email to you for details.
Try to answer part of the questions:
> Q2: from office tutorial of gluonCV with C++, seems it is feasible to
build with MKL+MKLDNN in cmd command. But with CMake Gui, USE_MKLDNN is
forbidden, as it need (NOT MSVC) . WHY?
It's possible to build MXNet with MKL/MKL-DNN from source. Please take a
look at what we do in CI:
https://github.com/apache/incubator-mxnet/blob/master/ci/docker/runtime_functions.sh#L553
https://github.com/apache/incubator-mxnet/blob/master/ci/docker/runtime_functions.sh#L708
I'm not a CMAKE GUI user, so not sure what's the problem on it.
> Q4: I googled a lot on MKl with mxnet, and I found a discussion within
mxnet team, with the content of the discussion and what I found in
downloadMKLML.cmake, does it mean mxnet recommand install MKLDNN with JUST
submodule of MKL at present(and it is still vague to decide whether submodule
of MKL is needed when building mxnet from source)?
Currently, it is much easier to get MKLML compared with to get full MKL. It
has more friendly license to mxnet, smaller binary size and more convenient
download source. So now it's the default behavior to download MKLML and link to
it when mxnet is built with USE_MKLDNN=1. But you're right, there is no need to
link MKLML if full MKL is installed and linked to mxnet.
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
With regards,
Apache Git Services
