From: Ferruh Yigit <ferruh.yigit@amd.com>
To: longli@microsoft.com, Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
Cc: dev@dpdk.org, stable@dpdk.org
Subject: Re: [PATCH] net/netvsc: increase VSP response timeout to 60 seconds
Date: Thu, 28 Sep 2023 19:01:52 +0100 [thread overview]
Message-ID: <19349304-2a8b-4414-98b9-8a718606501b@amd.com> (raw)
In-Reply-To: <1690410550-15636-1-git-send-email-longli@linuxonhyperv.com>
On 7/26/2023 11:29 PM, longli@linuxonhyperv.com wrote:
> From: Long Li <longli@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: stable@dpdk.org
> Signed-off-by: Long Li <longli@microsoft.com>
>
Applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2023-09-28 18:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-26 22:29 longli
2023-09-28 18:01 ` Ferruh Yigit [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=19349304-2a8b-4414-98b9-8a718606501b@amd.com \
--to=ferruh.yigit@amd.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=longli@microsoft.com \
--cc=stable@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).