Thanks for bringing this up, this is definitely on our radar! The initial [uTVM 
PR](https://github.com/apache/incubator-tvm/pull/5417) was intended to sync our 
prototype work, based on the [original 
RFC](https://github.com/apache/incubator-tvm/issues/2563), up to master. We'll 
have some initial results evaluating the prototype forthcoming soon.

At the same time, we realize that needing to hardcode lots of device specific 
things, such as the memory layout you've included here, won't scale as we 
expand. To that end, Tianqi submitted a [major 
refactor](https://github.com/apache/incubator-tvm/pull/5484) the TVM RPC 
subsystem. This refactor lays the groundwork to implement a TVM RPC server 
without the use of dynamic linking. You can see an example of that with the 
[Web Assembly PR](https://github.com/apache/incubator-tvm/pull/5506). We're 
planning to take a similar approach with µTVM, with a lot more flexibility in 
terms of compilation, linking, and the RPC transport layer. We should be 
posting a more detailed RFC this week.

I'm curious if that approach roughly aligns with your use case? I think it 
would be better to save discussion on implementation details for the 
forthcoming RFC, but happy to continue discussing at a high level on this 
thread.

-Andrew





---
[Visit 
Topic](https://discuss.tvm.ai/t/discuss-extending-utvm-micro-session-and-more-boards/6643/2)
 to respond.

You are receiving this because you enabled mailing list mode.

To unsubscribe from these emails, [click 
here](https://discuss.tvm.ai/email/unsubscribe/759c63143668d9394a49c6caccac03b3d7092fd26fdf264c60cafa7c9a0dfba6).

Reply via email to