All of lore.kernel.org
 help / color / mirror / Atom feed
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 v5] net/i40e: extend VF reset waiting time
Date: Thu, 29 Apr 2021 11:04:16 +0000	[thread overview]
Message-ID: <ca0f630c567f47e49729e945a0156b1d@intel.com> (raw)
In-Reply-To: <20210429082724.1157163-1-wenjun1.wu@intel.com>



> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of Wenjun Wu
> Sent: Thursday, April 29, 2021 4:27 PM
> To: dev@dpdk.org; Xing, Beilei <beilei.xing@intel.com>
> Cc: Wu, Wenjun1 <wenjun1.wu@intel.com>
> Subject: [dpdk-dev] [PATCH v5] net/i40e: extend VF reset waiting time
> 
> When starting VF, VF will issue reset command to PF, wait a fixed amount of
> time, and assume VF reset is done on PF side. However, compared with kernel
> PF, DPDK PF needs more time to setup. If we run DPDK PF to support DPDK VF,
> the original delay will not be enough. When we first start VF after PF is
> launched, the execution time of the statement info.msg_buf =
> rte_zmalloc("msg_buffer", info.buf_len, 0); in the function
> i40e_dev_handle_aq_msg is more than 200ms. It may cause VF start error.
> 
> Since iavf can hardly triggle this issue and i40evf will be replaced by iavf in
> future DPDK versions, this patch provide a workaround.
> We 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


      reply	other threads:[~2021-04-29 11:04 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
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 [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=ca0f630c567f47e49729e945a0156b1d@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.