-
Notifications
You must be signed in to change notification settings - Fork 3.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[microTVM] Fix RPC session close on runtime side #13310
Conversation
Thanks for contributing to TVM! Please refer to the contributing guidelines https://tvm.apache.org/docs/contribute/ for useful information and tips. Please request code reviews from Reviewers by @-ing them in a comment. Generated by tvm-bot |
e23bbc2
to
4347875
Compare
4347875
to
3361be6
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
CI / Android failed. I'm re-triggering. |
@tvm-bot rerun |
@mehrdadh Thank you. The change is now merged. |
Currently, the RPC session on C/C++ side does not know if the session was closed on Python side which causes extra read/write on transport while the session is already closed. This commit reuses the Hexagon approach in microTVM to shutdown the RPC session.
Currently, the RPC session on C/C++ side does not know if the session was closed on Python side which causes extra read/write on transport while the session is already closed. This commit reuses the Hexagon approach in microTVM to shutdown the RPC session.
Currently, the RPC session on C/C++ side does not know if the session was closed on python side which causes extra read/write on transport while the session is already closed. This PR reuses the hexagon approach in microTVM to shutdown the RPC session.