patches for DPDK stable branches
 help / color / mirror / Atom feed
From: "Xueming(Steven) Li" <xuemingl@nvidia.com>
To: "chenqiming_huawei@163.com" <chenqiming_huawei@163.com>,
	"stable@dpdk.org" <stable@dpdk.org>
Cc: "beilei.xing@intel.com" <beilei.xing@intel.com>
Subject: Re: [dpdk-stable] [PATCH 20.11] net/i40evf: extend the polling times of vf reset
Date: Mon, 8 Nov 2021 12:04:27 +0000	[thread overview]
Message-ID: <f4f58e663dae7315a00276648ebf8d38d4b0b064.camel@nvidia.com> (raw)
In-Reply-To: <20210909091320.10736-1-chenqiming_huawei@163.com>

On Thu, 2021-09-09 at 17:13 +0800, Qiming Chen wrote:
> In the embedded RTOS environment, the x722 controller Ethernet card of
> the d2146nt chip, the vfio user mode driver takes over 8 vf ports in
> turn, but i40evf_check_vf_reset_done will probably fail.
> 
> The version matching is no problem, and there is no
> substantial progress. Learning from the implementation
> of the i40evf kernel driver locally, after modifying the polling time
> from 1 second to 5s, the repeated restart process took over the start
> port test, and it was found that this probability was reduced to an
> order of magnitude acceptable to the user.
> 
> The patch cannot fundamentally solve the failure problem, but it greatly
> slows down the probability of the problem. The modification is based on the
> i40evf kernel driver.
> 
> Fixes: 4861cde46116 ("i40e: new poll mode driver")
> 
> Signed-off-by: Qiming Chen <chenqiming_huawei@163.com>
> ---
>  drivers/net/i40e/i40e_ethdev_vf.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/net/i40e/i40e_ethdev_vf.c b/drivers/net/i40e/i40e_ethdev_vf.c
> index f64db72e9a..924da8dfb4 100644
> --- a/drivers/net/i40e/i40e_ethdev_vf.c
> +++ b/drivers/net/i40e/i40e_ethdev_vf.c
> @@ -42,7 +42,7 @@
>  /* busy wait delay in msec */
>  #define I40EVF_BUSY_WAIT_DELAY 10
>  #define I40EVF_BUSY_WAIT_COUNT 50
> -#define MAX_RESET_WAIT_CNT     20
> +#define MAX_RESET_WAIT_CNT     100
>  
>  #define I40EVF_ALARM_INTERVAL 50000 /* us */
>  

Hi Qiming,

This is v2 patch, add "-v 2" in format-patch command, "[v2]" will
appear in subject. Also add v1 mail Message-Id to reply in send-email
command to make v2 patch in the tree of v1. Message-Id can be found in
either your email client or http://inbox.dpdk.org/stable/.

Applied to 20.11.4, thanks!

Regards,
Xueming


      reply	other threads:[~2021-11-08 12:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-09  9:13 Qiming Chen
2021-11-08 12:04 ` Xueming(Steven) Li [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=f4f58e663dae7315a00276648ebf8d38d4b0b064.camel@nvidia.com \
    --to=xuemingl@nvidia.com \
    --cc=beilei.xing@intel.com \
    --cc=chenqiming_huawei@163.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).