[RFC][Backend] RFC-CSI-NN2-Integration

[alter-xp]

Introduce CSI-NN2 Compute Library into TVM to accelerate the inference performance of RISC-V CPU with Vector Extension.

@areusch

[hogepodge]

This is fantastic, thank you! We're excited to hear about the results for MLPerf. My main comment is mostly concerned about documentation. I'm glad the build instructions are included with the RFC, but I'd like to see the inclusion of documentation about how to configure, build, and use the platform be explicitly updated and included.

[areusch]

@alter-xp thanks for the rfc! I added a couple questions for you, but overall this looks pretty good.

[alter-xp]

This is fantastic, thank you! We're excited to hear about the results for MLPerf. My main comment is mostly concerned about documentation. I'm glad the build instructions are included with the RFC, but I'd like to see the inclusion of documentation about how to configure, build, and use the platform be explicitly updated and included.

Thanks for comments. we provide a documentation in PR for TVM. But I'm not sure whether these contents need to be completely written in RPC

[areusch]

thanks @alter-xp , couple more follow-ups here

[alter-xp]

ok, then for CI do you plan to e.g. expand our ci_qemu Docker image to additionally contain this custom qemu? (this involves committing a change to docker/, then pinging a committer to update the version of the image used)

Thanks for advice, we will add it. but I have no experience about this. Is there any relevant process?

[areusch]

@alter-xp we have some:

• about the CI environment: https://tvm.apache.org/docs/contribute/pull_request.html#ci-environment
• about building docker containers locally: https://github.com/apache/tvm/blob/main/docker/README.md

we need to write that up :/

the basics are:

1. submit a PR which only modifies docker/ scripts. the CI will rebuild docker containers and then run through using the newly-rebuilt containers.
2. ping a committer to publish the built images to the tlcpack dockerhub org
3. submit another PR which modifies jenkins/Jenkinsfile.j2 (and run generate.py there to modify Jenkinsfile) to reference the newly-pushed containers. you can also add tests which depend on the newly-added dependencies here.

[alter-xp]

@areusch Thanks a lot. let me update the image.

[areusch]

thanks @alter-xp ! @kparzysz-quic any final comments? i'll merge in a day if i don't hear anything.

[areusch]

thanks @alter-xp, the PR is now merged! please open an RFC tracking issue and list out the PRs we can expect there, then we can proceed on the CI changes.

[alter-xp]

@areusch a tracking issue is ready. I will keep updating it.