Yes, we want to continue this. However, I have other projects which taken most
of my time recently. We may come back a few months later. Thanks
---
[Visit
Topic](https://discuss.tvm.apache.org/t/byoc-add-verisilicons-npu-support/11097/11)
to respond.
You are receiving this because you en
@sven what's the status on this RFC? Is it something you're still interested in
contributing?
---
[Visit
Topic](https://discuss.tvm.apache.org/t/byoc-add-verisilicons-npu-support/11097/10)
to respond.
You are receiving this because you enabled mailing list mode.
To unsubscribe from thes
Closed #32.
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm-rfcs/pull/32#event-6302449499
You are receiving this because you are subscribed to this thread.
Message ID:
closing due to lack of response
--
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm-rfcs/pull/32#issuecomment-1078221738
You are receiving this because you are subscribed to this thread.
Message ID:
> Is there a model being developed to estimate latency of the chosen
> partitioning?
No. As far as Collage is concerned it just calls the abstract
CostEstimator::Estimate interface for each candidate partition, and can remain
ignorant as to where those costs come from. In the prototype it is h
> 1.) How can a user export the search done by collage ? i.e. similar to
> loading tuning logs where ApplyBestHistory is done.
Having thought about this more, If there can be a way to define a PartitionSpec
that is tied with DFS IndexSet that could be exported and imported, that might
work out.
