We do support layout conversion passes, what you talked about is related to
AlterOpLayout pass. see related discussions
https://discuss.tvm.ai/t/rfc-functionality-of-alteroplayout-and-possible-refactoring/1999
---
[Visit
Topic](https://discuss.tvm.ai/t/use-block-data-format-for-whole-mode
Ok, if I understood this example correctly here is a way to take advantage of
NCHWc in case of model already being in this format. What I'm looking for is
more universal approach, allowing to convert whole model to NCHWc **and not
each operation**.
---
[Visit
Topic](https://discuss.tvm.a
Check this tutorial out which tunes networks to take advantage of AVX512, and
thus imposes NCHWc constraint on the data layout:
https://docs.tvm.ai/tutorials/autotvm/tune_nnvm_x86.html
---
[Visit
Topic](https://discuss.tvm.ai/t/use-block-data-format-for-whole-model/3693/2)
to respond.
Y
I'd like to ask if there is any plan or any simple way to enable block (NCHWc)
data format for whole model instead of plain (NCHW)?
After some playing with TVM it seems that the preferred data type is plain.
Significant exceptions are for Intel CPU and Intel Graphics scheduler which are
capab
