You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tvm.apache.org by Mehrdad Hessar <no...@github.com.INVALID> on 2022/05/31 16:25:00 UTC

[apache/tvm-rfcs] [RFC][MLF] Model Library Format with Multiple Modules (PR #76)

This RFC proposes adding multiple module support in Model Library Format.

cc @gromero @areusch 
You can view, comment on, or merge this pull request online at:

  https://github.com/apache/tvm-rfcs/pull/76

-- Commit Summary --

  * MLF with Multiple Module RFC

-- File Changes --

    A rfcs/0075_mlf_with_multiple_modules.md (162)

-- Patch Links --

https://github.com/apache/tvm-rfcs/pull/76.patch
https://github.com/apache/tvm-rfcs/pull/76.diff

-- 
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm-rfcs/pull/76
You are receiving this because you are subscribed to this thread.

Message ID: &lt;apache/tvm-rfcs/pull/76@github.com&gt;

Re: [apache/tvm-rfcs] [RFC][MLF] Model Library Format with Multiple Modules (PR #76)

Posted by Gustavo Romero <no...@github.com.INVALID>.

Merged #76 into main.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm-rfcs/pull/76#event-6757119416
You are receiving this because you are subscribed to this thread.

Message ID: <ap...@github.com>

Re: [apache/tvm-rfcs] [RFC][MLF] Model Library Format with Multiple Modules (PR #76)

Posted by Andrew Reusch <no...@github.com.INVALID>.

cc @Mousius @manupa-arm @leandron 

-- 
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm-rfcs/pull/76#issuecomment-1142686653
You are receiving this because you are subscribed to this thread.

Message ID: <ap...@github.com>

Re: [apache/tvm-rfcs] [RFC][MLF] Model Library Format with Multiple Modules (PR #76)

Posted by driazati <no...@github.com.INVALID>.

Discussion in the community meeting was pretty supportive! Some summary notes:

* Name prefix option makes sense, change seems like a natural evolution of MLF
* Before users would have to do the same thing by hand
* Is the deserializer going to be backwards compatible?
  * No loader in C++ runtime, only in project API. Eventually MLF scope will expand to include other things like multiple devices, so C++ loader might be useful later on. Code typically used along with the same TVM revision so no need to keep around the old loader. The version number can be used to provide helpful error messages.
* It would be good to add a description for users on what needs to change, if anything and reference documentation


-- 
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm-rfcs/pull/76#issuecomment-1143757173
You are receiving this because you are subscribed to this thread.

Message ID: <ap...@github.com>