From: Long Li <lon...@microsoft.com> The current timeout is set to 5 seconds. In Azure, tests show that it may take up to 15 seconds for VSP to respond on busy nodes. The VSP schedules unbounded work to process VSC resquest, there is no upper limit on how long it takes to send response back to VSC.
In the NETVSC kernel mode driver, it waits forever for VSP response. While in DPDK we can't wait forever, setting the timeout to 60 seconds. Cc: sta...@dpdk.org Signed-off-by: Long Li <lon...@microsoft.com> --- drivers/net/netvsc/hn_rndis.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/net/netvsc/hn_rndis.c b/drivers/net/netvsc/hn_rndis.c index e6f1f28768..7e9abce8d0 100644 --- a/drivers/net/netvsc/hn_rndis.c +++ b/drivers/net/netvsc/hn_rndis.c @@ -35,7 +35,7 @@ #include "hn_rndis.h" #include "ndis.h" -#define RNDIS_TIMEOUT_SEC 5 +#define RNDIS_TIMEOUT_SEC 60 #define RNDIS_DELAY_MS 10 #define HN_RNDIS_XFER_SIZE 0x4000 -- 2.17.1
