[GitHub] [tvm-rfcs] mbaret commented on pull request #37: Introduce the Arm(R) Ethos(TM)-U Cascading Planner

[GitBox <gi...@apache.org>]

mbaret commented on pull request #37:
URL: https://github.com/apache/tvm-rfcs/pull/37#issuecomment-957953894


   > @mbaret thanks for the detailed RFC! i think my main questions here are whether or not this could be implemented in roughly two pieces similar to USMP:
   > 
   >     1. a piece which could be reused if we e.g. wanted to attempt to apply this to non-Ethos-U kernels
   > 
   >     2. the Ethos-U-specific logic.
   > 
   > 
   > I understand it may not make sense to integrate with AutoTVM--it might make more sense to wait til TensorIR has fully landed. but just curious to understand in planning terms what the lift might be.
   
   Apologies for the late reply @areusch. Due to some of the uncertainties around implementing this generically (Relay fusion/conflict with AutoTVM/deriving matrices), I think it's more pragmatic to have everything initially scoped just to Ethos-U. But within that implementation, all the truly Ethos-U specific logic is quite self-contained (pretty much entirely in the performance heuristics and matrix definitions). Therefore, should this need reusing in future we could probably lift it out of the Ethos-U namespace. I think this would be very doable as the cascader itself is quite well decoupled from the rest of the Ethos-U compiler, exposing only a TE Schedule -> TE Schedule interface. With some effort, although hopefully not too much, that interface could likely be tweaked to be TensorIR -> TensorIR.


-- 
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.

To unsubscribe, e-mail: commits-unsubscribe@tvm.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org