Thanks for @driazati @areusch to bring this for discussion, I think it make
sense to reduce the notification spam by rename the codeowner file, and
definitely that can help contributor to focus on more related message from
community.
I agree with @comaniac @manupa-arm about helping the new
Hi @comaniac , subgraph executor get renamed into pipeline executor, and the PR
now only include pipeline executor and schedule logic, could you help for a
review?
---
[Visit
Topic](https://discuss.tvm.apache.org/t/rfc-compute-graph-pipeline-with-new-subgraph-executor/9839/7)
to respond.
@tqchen @comaniac @areusch @tmoreau89 @zhiics @giuseros.
---
[Visit
Topic](https://discuss.tvm.apache.org/t/rfc-compute-graph-pipeline-with-new-subgraph-executor/9839/2)
to respond.
You are receiving this because you enabled mailing list mode.
To unsubscribe from these emails, [click
he
Thanks @comaniac @zhiics @giuseros @JaydeepIMG @JakeStevens for the review and
discussion.
The compute pipeline runtime/executor PR already get
submitted(https://github.com/apache/tvm/pull/7892) , I also propose a new
RFC(https://discuss.tvm.apache.org/t/rfc-compute-graph-pipeline-with-new-s
>This is a follow up RFC for
>https://discuss.tvm.apache.org/t/compute-graph-pipeline/8957
>PR https://github.com/apache/tvm/pull/7892
# **Split relay graph into Subgraph then doing Subgraph Pipeline :RFC**
In this RFC, we present a new framework for subgraph pipelining that first
split rela
@hht, thanks for this post, problem the said solution try to addressed pretty
like this April PR https://github.com/apache/incubator-tvm-vta/pull/7 by
@zhanghaohit , could you help to verify if this #7 independently can fix your
problem without the said verilog change?
---
[Visit Topic]
