Re: Proposal - Design of CNML/CNRT Integration

2019-07-08 Thread Skalicky, Sam
Hi Yan Zhe,

I am very excited about Cambricon’s proposal to integrate with MXNet. The 
proposal is quite comprehensive, but one piece that I find missing is the graph 
partitioning piece. In your proposal you mention that CNML may not support all 
MXNet operators, and so some parts may run on the host device. Are you planning 
to do something similar to how TensorRT integrated with MXNet? They also have 
to do a “compile” and convert parts of the graph to their own format for 
execution. Here is the PR with their recent changes supporting the subgraph API:

https://github.com/apache/incubator-mxnet/pull/14040

You can take a look at how they did it to get a better idea if the same can 
work for you.

I think the level of integration you propose is quite extensive and with touch 
all the underlying components of MXNet (and its dependencies in TVM/NNVM). So 
I’m not sure if thats the right approach, since it will take a lot of time to 
make all the changes and test that nothing has broken. Intel’s changes for 
MKLDNN touched quite a few pieces but not as much as you’re proposing. I would 
like to see a retrospective from Intel at some point on how they think their 
integration went and if we can make it better for the next time (ie. Cambricon).

Thanks Tao for the Accelerator proposal plug! While I would like to see 
Cambricon’s accelerator use that work, I don’t want to hold up their 
integration to MXNet. We are just getting started with this work. Our next 
milestone is to put up an initial WIP PR and discuss with the community, so I’m 
not sure that that is the preferred approach (since it hasn’t been accepted by 
the community yet, either).

Sam


On Jul 4, 2019, at 12:55 AM, 严哲 
mailto:yan...@cambricon.com>> wrote:

Hi Tao,

Thanks for your suggestions.

I have read the proposal "Bring your own Accelerator". The feature it proposed 
is excellent. After reading the proposal, I have two questions:

1. If our current design shown in the proposal "Design of CNML/CNRT 
Integration" is feasible ?

2. If the way proposed in "Bring your own Accelerator" is preferred, we will 
refactor our design toward that way. In this case, I want to know if the 
feature in "Bring your own Accelerator" is approved and in the plan ?


-原始邮件-
发件人: "Lv, Tao A" mailto:tao.a...@intel.com>>
发送时间: 2019-06-28 17:46:22 (星期五)
收件人: "dev@mxnet.incubator.apache.org" 
mailto:dev@mxnet.incubator.apache.org>>, 
"d...@mxnet.apache.org" 
mailto:d...@mxnet.apache.org>>
抄送: "yan...@cambricon.com" 
mailto:yan...@cambricon.com>>
主题: RE: Proposal - Design of CNML/CNRT Integration

Hi Yan Zhe,

Thanks for the nice proposal. In case you didn't know, there is a meta proposal 
for bringing new accelerator to MXNet: 
https://cwiki.apache.org/confluence/display/MXNET/Bring+your+own+Accelerator

Before reading in details, I'm curious to know whether you have any performance 
data for the proposal and what's the validation plan for a new hardware backend?

Thanks,
-tao


-Original Message-
From: 严哲 [mailto:yan...@cambricon.com]
Sent: Friday, June 28, 2019 4:42 PM
To: d...@mxnet.apache.org
Subject: Proposal - Design of CNML/CNRT Integration

Hello Community,



I am from Cambricon which is a company developing machine learning processors.


Now I have written a proposal that introduces the design of integrating 
CNML(Cambricon Neuware Machine Learning Library) / CNRT(Cambricon Neuware 
Runtime Library) into MXNet. After integrating with CNML/CNRT, developers can 
work with MXNet on Cambricon machine learning processors.


I am looking forward to your precious suggestions,  especially the suggestions 
considering recent updates about MXNet version 1.5.0. Any feedback and help 
will be greatly appreciated.


Design proposal: 
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=120722127


Thanks & BestRegards,

YanZhe


--
Thanks & Best Regards,
Yan Zhe



Re: [VOTE] Release Apache MXNet (incubating) version 1.5.0.rc2

2019-07-08 Thread Qing Lan
Hi All,

I found the problem when I tried to build from source with my Mac:

clang: error: unsupported option '-fopenmp'
clang: error: unsupported option '-fopenmp'
make: *** [build/src/operator/nn/mkldnn/mkldnn_act.o] Error 1
make: *** [build/src/operator/nn/cudnn/cudnn_batch_norm.o] Error 1

I use "make -j4" with tar.gz package

Thanks,
Qing




From: Sheng Zha 
Sent: Friday, July 5, 2019 17:42
To: d...@mxnet.apache.org
Subject: Re: [VOTE] Release Apache MXNet (incubating) version 1.5.0.rc2

+1

On 2019/06/27 17:05:40, Lai Wei  wrote:
> Dear MXNet community,
>
> This is the 3-day vote to release Apache MXNet (incubating) version 1.5.0.
> Voting on dev@ will start June 26, 23:59:59(PST)  and close on June 29,
> 23:59:59.
>
> 1) Link to release notes:
> https://cwiki.apache.org/confluence/display/MXNET/1.5.0+Release+Notes
>
>
> 2) Link to release candidate:
>
> https://github.com/apache/incubator-mxnet/releases/tag/1.5.0.rc2
>
>
>
> 3) Link to source and signatures on apache dist server:
>
> https://dist.apache.org/repos/dist/dev/incubator/mxnet/1.5.0.rc2/
>
>
>
> Please remember to TEST first before voting accordingly:
>
> +1 = approve
> +0 = no opinion
> -1 = disapprove (provide reason)
> --
> Best Regards
>
> Lai
>