From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: "Wu, Wenjun1" <wenjun1.wu@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"Xing, Beilei" <beilei.xing@intel.com>
Cc: "Wu, Wenjun1" <wenjun1.wu@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2] net/i40e: extend VF reset waiting time
Date: Sun, 25 Apr 2021 02:25:35 +0000 [thread overview]
Message-ID: <bede2047c74b4d0aab83802bca0ad8cf@intel.com> (raw)
In-Reply-To: <20210425020250.205597-1-wenjun1.wu@intel.com>
> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of Wenjun Wu
> Sent: Sunday, April 25, 2021 10:03 AM
> To: dev@dpdk.org; Xing, Beilei <beilei.xing@intel.com>
> Cc: Wu, Wenjun1 <wenjun1.wu@intel.com>
> Subject: [dpdk-dev] [PATCH v2] net/i40e: extend VF reset waiting time
>
> When resetting VF, VF will issue reset command to PF, wait a fixed amount of
> time, and assume VF reset is done. However, due to the change of dpdk
> related library content, the original delay is not enough. When we use DPDK
> PF instead of kernel PF, it may cause VF start error.
>
> This patch extend VF reset waiting time from 200ms to 500ms so that VF can
> start normally when using DPDK PF and DPDK VF in most cases.
>
> Signed-off-by: Wenjun Wu <wenjun1.wu@intel.com>
Acked-by: Qi Zhang <qi.z.zhang@intel.com>
Applied to dpdk-next-net-intel.
Thanks
Qi
next prev parent reply other threads:[~2021-04-25 2:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-22 5:34 [dpdk-dev] [PATCH v1] net/i40e: extend VF reset waiting time Wenjun Wu
2021-04-25 2:02 ` [dpdk-dev] [PATCH v2] " Wenjun Wu
2021-04-25 2:25 ` Zhang, Qi Z [this message]
2021-04-25 7:44 ` Zhou, JunX W
2021-04-28 9:30 ` Ferruh Yigit
2021-04-29 2:26 ` Wu, Wenjun1
2021-04-29 3:05 ` [dpdk-dev] [PATCH v3] " Wenjun Wu
2021-04-29 3:10 ` [dpdk-dev] [PATCH v4] " Wenjun Wu
2021-04-29 8:27 ` [dpdk-dev] [PATCH v5] " Wenjun Wu
2021-04-29 11:04 ` Zhang, Qi Z
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=bede2047c74b4d0aab83802bca0ad8cf@intel.com \
--to=qi.z.zhang@intel.com \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=wenjun1.wu@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.