From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: "Zeng, ZhichaoX" <zhichaox.zeng@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "Wang, Liang-min" <liang-min.wang@intel.com>,
"Wu, Jingjing" <jingjing.wu@intel.com>,
"Xing, Beilei" <beilei.xing@intel.com>
Subject: RE: [PATCH v2] net/iavf: add VF reset check
Date: Fri, 2 Jun 2023 03:25:41 +0000 [thread overview]
Message-ID: <DM4PR11MB599483601B2E83E2C953B69AD74EA@DM4PR11MB5994.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20230602023822.2370902-1-zhichaox.zeng@intel.com>
> -----Original Message-----
> From: Zeng, ZhichaoX <zhichaox.zeng@intel.com>
> Sent: Friday, June 2, 2023 10:38 AM
> To: dev@dpdk.org
> Cc: Zhang, Qi Z <qi.z.zhang@intel.com>; Zeng, ZhichaoX
> <zhichaox.zeng@intel.com>; Wang, Liang-min <liang-min.wang@intel.com>;
> Wu, Jingjing <jingjing.wu@intel.com>; Xing, Beilei <beilei.xing@intel.com>
> Subject: [PATCH v2] net/iavf: add VF reset check
>
> In the current implementation, after application calls rte_eth_dev_reset, it
> has no way to know if reset has been completed, and if the virtual channel
> command is called before it is completed, it may cause the dev to be
> abnormal. To avoid this issue, an uncertain delay need to be added.
>
> This commit adds a VF reset check before the dev_reset to inform the
> application not to invoke any virtual channel commands, to avoid making the
> device to be abnormal.
>
> Suggested-by: Liang-Min Larry Wang <liang-min.wang@intel.com>
> Signed-off-by: Zhichao Zeng <zhichaox.zeng@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:[~2023-06-02 3:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-25 2:17 [PATCH] " Zhichao Zeng
2023-06-02 2:38 ` [PATCH v2] " Zhichao Zeng
2023-06-02 3:25 ` Zhang, Qi Z [this message]
2023-06-02 2:37 Zhichao Zeng
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=DM4PR11MB599483601B2E83E2C953B69AD74EA@DM4PR11MB5994.namprd11.prod.outlook.com \
--to=qi.z.zhang@intel.com \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=jingjing.wu@intel.com \
--cc=liang-min.wang@intel.com \
--cc=zhichaox.zeng@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 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).