From: "Chen, LingliX" <linglix.chen@intel.com>
To: "Xing, Beilei" <beilei.xing@intel.com>,
"Zhang, Qi Z" <qi.z.zhang@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"Xing, Beilei" <beilei.xing@intel.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH v2] net/i40e: fix FDIR input set conflict issue
Date: Thu, 24 Jun 2021 09:34:38 +0000 [thread overview]
Message-ID: <CO1PR11MB488407A78EDB02D1DDA0653990079@CO1PR11MB4884.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20210624072956.45489-1-beilei.xing@intel.com>
> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of beilei.xing@intel.com
> Sent: Thursday, June 24, 2021 3:30 PM
> To: Zhang, Qi Z <qi.z.zhang@intel.com>
> Cc: dev@dpdk.org; Xing, Beilei <beilei.xing@intel.com>; stable@dpdk.org
> Subject: [dpdk-dev] [PATCH v2] net/i40e: fix FDIR input set conflict issue
>
> From: Beilei Xing <beilei.xing@intel.com>
>
> Currently, there'll be conflict error when running the following commands:
> 1. flow create 0 ingress
> pattern eth / ipv4 / udp src is 32 / end
> actions queue index 2 / end
> 2. flow destroy 0 rule 0
> 3. flow create 0 ingress
> pattern eth / ipv4 / udp dst is 32 / end
> actions queue index 2 / end
>
> This patch fixes the input set conflict issue.
>
> Fixes: 42044b69c67d ("net/i40e: support input set selection for FDIR")
> Fixes: 4a072ad43442 ("net/i40e: fix flow director config after flow validate")
> Cc: stable@dpdk.org
>
> Signed-off-by: Beilei Xing <beilei.xing@intel.com>
Tested-by: Lingli Chen <linglix.chen@intel.com>
next prev parent reply other threads:[~2021-06-24 9:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-24 7:07 [dpdk-stable] [PATCH] " beilei.xing
2021-06-24 7:29 ` [dpdk-stable] [PATCH v2] " beilei.xing
2021-06-24 9:34 ` Chen, LingliX [this message]
2021-06-30 2:00 ` [dpdk-stable] [dpdk-dev] " 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=CO1PR11MB488407A78EDB02D1DDA0653990079@CO1PR11MB4884.namprd11.prod.outlook.com \
--to=linglix.chen@intel.com \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=qi.z.zhang@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).