have 'mxnet' package without MKL-DNN backend and 'mxnet-mkl' with
MKL-DNN backend.
-tao
-Original Message-
From: Lv, Tao A [mailto:tao.a...@intel.com]
Sent: Tuesday, January 15, 2019 8:14 AM
To: dev@mxnet.incubator.apache.org
Subject: Re: [DISCUSS] Make MKLDNN as a default on Maven nightly
MKLML has already been released with mxnet-mkl for 4 versions: 1.2.0, 1.2.1,
1.3.0, 1.3.1.
> On Jan 15, 2019, at 3:43 AM, Zach Kimberg wrote:
>
> There should not be a problem including MKLML since the above (BSD
> 3-clause) is Category A under apache (
>
There should not be a problem including MKLML since the above (BSD
3-clause) is Category A under apache (
https://www.apache.org/legal/resolved.html#what-can-we-include-in-an-asf-project-category-a
).
However, what I noticed from some other apache projects is they created
additional LICENSE files
+1 if the licensing aspect is ok. Since MKLDNN (open source apache 2
license) depends on MKLML (binary only) which carries its own license (see
below for the full text), we need to check if it's ok to include this
license in our binary distribution. Full text of the MKLML license:
Copyright (c)
Thanks for bringing this up.
I think it would be less confusing for users if we keep it same across
language bindings? What needs to be done to python, Java, Clojure, etc., ?
If they are not getting this default, any reason?
On Mon, Jan 14, 2019 at 10:56 AM Qing Lan wrote:
> Hi all,
>
> I would
Hi all,
I would like to raise a discussion on whether to make MKLDNN as a default in
nightly build (1.5.0-SNAPSHOT) for MXNet Scala/Java binding. Currently Scala
build with MKLDNN is supported since
https://github.com/apache/incubator-mxnet/pull/13819 with CI. I do see the
performance
