tvm-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Zhao Wu <>
Subject Re: [dmlc/tvm] [RFC] Frontend layout transformation (#2519)
Date Wed, 17 Apr 2019 15:04:47 GMT
@tqchen I plan to support TFLite NHWC data layout after my quantization part upstreamed.  However,
NCHW has its advantages as described.  We could have two options:

- Keep NCHW of TFLite and add one parameter named `layout` in `from_tflite`.

`layout` could be `NCHW` or `NHWC`. The default value could be discussed. This means we support
two data layout in TFLite frontend and leave decisions to user. For example, user want to
use `NCHW[x]c` schedule or model has `conv2d_transpose`, they may want to use NCHW layout.

- Drop NCHW of TFLite and  only original TFLite NHWC layout.

Besides TFLite frontend work, we also should have some work in AutoTVM (support NHWC of convolution
tuning) and support `spatial pack` NHWC on ARM CPU.

Wish to hear some comments of yours.

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
  • Unnamed multipart/alternative (inline, 7-Bit, 0 bytes)
View raw message