DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: "Yu, DapengX" <dapengx.yu@intel.com>,
	"Yang, Qiming" <qiming.yang@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v5] net/ice: simplify the use of DCF device reset
Date: Wed, 27 Oct 2021 03:24:51 +0000	[thread overview]
Message-ID: <ad64158a5b1e47efaa76ed12b288c81d@intel.com> (raw)
In-Reply-To: <20211026095308.1759784-1-dapengx.yu@intel.com>



> -----Original Message-----
> From: Yu, DapengX <dapengx.yu@intel.com>
> Sent: Tuesday, October 26, 2021 5:53 PM
> To: Yang, Qiming <qiming.yang@intel.com>; Zhang, Qi Z
> <qi.z.zhang@intel.com>
> Cc: dev@dpdk.org; Yu, DapengX <dapengx.yu@intel.com>; stable@dpdk.org
> Subject: [PATCH v5] net/ice: simplify the use of DCF device reset

It's a workaround, so rename to 

"workaround DCF reset failure"

> 
> From: Dapeng Yu <dapengx.yu@intel.com>
> 
> After DCF is reset by PF, the DCF device un-initialization cannot function
> normally since the kernel may not clean up resource.
> 
> This patch detects the reset flag, which is set by PF on DCF reset, if the flag is
> true, reset hw to trigger an additional DCF enable/disable cycle which helps to
> work around the issue that kernel driver may not clean up resource during
> previous reset.

Reword to

After DCF is reset by PF, the DCF device un-initialization cannot
function normally, ignore the failure does not help since the kernel
does not clean up resource.

The patch workaround the issue by triggering an additional DCF enable/
disable cycle when a passive reset is detected.

> 
> Fixes: 1a86f4dbdf42 ("net/ice: support DCF device reset")
> Cc: stable@dpdk.org
> 
> Signed-off-by: Dapeng Yu <dapengx.yu@intel.com>

Acked-by: Qi Zhang <qi.z.zhang@intel.com>

Applied to dpdk-next-net-intel.

Thanks
Qi


      reply	other threads:[~2021-10-27  3:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-25  6:41 [dpdk-dev] [PATCH] " dapengx.yu
2021-10-25  7:12 ` [dpdk-dev] [PATCH v2] " dapengx.yu
2021-10-26  8:18   ` [dpdk-dev] [PATCH v3] " dapengx.yu
2021-10-26  8:44     ` [dpdk-dev] [PATCH v4] " dapengx.yu
2021-10-26  8:55       ` Zhang, Qi Z
2021-10-26  9:53       ` [dpdk-dev] [PATCH v5] " dapengx.yu
2021-10-27  3:24         ` 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=ad64158a5b1e47efaa76ed12b288c81d@intel.com \
    --to=qi.z.zhang@intel.com \
    --cc=dapengx.yu@intel.com \
    --cc=dev@dpdk.org \
    --cc=qiming.yang@intel.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).