From: "Wang, Haiyue" <haiyue.wang@intel.com>
To: "Yu, DapengX" <dapengx.yu@intel.com>,
"Yang, Qiming" <qiming.yang@intel.com>,
"Zhang, Qi Z" <qi.z.zhang@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "stable@dpdk.org" <stable@dpdk.org>
Subject: RE: [PATCH v2] net/ice: track the DCF state of PF
Date: Fri, 26 Nov 2021 03:17:12 +0000 [thread overview]
Message-ID: <DM4PR11MB5518C2D708669D53FC0814CFF7639@DM4PR11MB5518.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20211124081220.367596-1-dapengx.yu@intel.com>
> -----Original Message-----
> From: Yu, DapengX <dapengx.yu@intel.com>
> Sent: Wednesday, November 24, 2021 16:12
> To: Yang, Qiming <qiming.yang@intel.com>; Zhang, Qi Z <qi.z.zhang@intel.com>
> Cc: dev@dpdk.org; Wang, Haiyue <haiyue.wang@intel.com>; Yu, DapengX <dapengx.yu@intel.com>;
> stable@dpdk.org
> Subject: [PATCH v2] net/ice: track the DCF state of PF
>
> From: Dapeng Yu <dapengx.yu@intel.com>
>
> When VF is reset, PF will change DCF state from ON to other state, if
> flow creation, destroy, or redirect command is sent to DCF at this
> time, it will fail.
>
> This patch tracks DCF state and returns try-again error to caller when
> DCF state is not ON.
>
> Cc: stable@dpdk.org
>
> Signed-off-by: Dapeng Yu <dapengx.yu@intel.com>
> ---
> V2:
> * Move DCF state flag to another position
> ---
> drivers/net/ice/ice_dcf_ethdev.c | 12 ++++++++
> drivers/net/ice/ice_dcf_ethdev.h | 1 +
> drivers/net/ice/ice_dcf_parent.c | 16 +++++++---
> drivers/net/ice/ice_ethdev.h | 2 ++
> drivers/net/ice/ice_generic_flow.c | 4 ++-
> drivers/net/ice/ice_switch_filter.c | 45 +++++++++++++++++++++++++++--
> 6 files changed, 73 insertions(+), 7 deletions(-)
>
LGTM,
Acked-by: Haiyue Wang <haiyue.wang@intel.com>
> --
> 2.27.0
next prev parent reply other threads:[~2021-11-26 3:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-22 9:29 [PATCH] " dapengx.yu
2021-11-24 8:12 ` [PATCH v2] " dapengx.yu
2021-11-26 3:17 ` Wang, Haiyue [this message]
2022-01-02 8:29 ` 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=DM4PR11MB5518C2D708669D53FC0814CFF7639@DM4PR11MB5518.namprd11.prod.outlook.com \
--to=haiyue.wang@intel.com \
--cc=dapengx.yu@intel.com \
--cc=dev@dpdk.org \
--cc=qi.z.zhang@intel.com \
--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).