Well, I think there are two basic approaches.
(1) The interface between TVM and the Platform Provider is just a Python API. Whether or not there happen to be separate processes/commands/whatever is hidden behind that API. So a Platform Provider simply implements the Platform Provider Python API invoked by TVM. This seems to be the most flexible. Maybe this is what you had in mind originally? (2) If we want to standardize the "wire protocol" between the Platform Provider and TVM, I'd recommend just using gRPC or something similar, since it is well supported in Python, easy to integrate, and does not limit you in terms of where the client/server are running (they can be on the same machine or even in the same process). The main reason to do this would be to make Platform Providers pluggable at the wire protocol level rather than the Python API level. I am not sure whether this is important or not. --- [Visit Topic](https://discuss.tvm.apache.org/t/tvm-mini-map-the-tvm-developer-workflow/9045/8) to respond. You are receiving this because you enabled mailing list mode. To unsubscribe from these emails, [click here](https://discuss.tvm.apache.org/email/unsubscribe/f36cfa9622b0c9f78b41b2bf136076db394f85ec25fc739e09cf5f319d0555f9).
