You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@tvm.apache.org by GitBox <gi...@apache.org> on 2022/04/08 21:57:34 UTC

[GitHub] [tvm] kparzysz-quic commented on pull request #10945: [Hexagon] Handle TCP server binding to unknown port

kparzysz-quic commented on PR #10945:
URL: https://github.com/apache/tvm/pull/10945#issuecomment-1093393396

   To add more context here: the RPC server will connect to a first available port in some range (which typically starts at 7070).  If there are two servers running on the same machine, one of them will get 7070, and the other 7071.  The clients will not know the actual port, instead they will query the RPC tracker for a server with a given device key.  Since the Hexagon RPC server always used the same key, the tracker could not distinguish between the one bound to 7070, and the one bound to 7071.  To avoid this ambiguity, make the device key unique (by attaching the PID of the process creating it to it).


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@tvm.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org