From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: "Zhang, AlvinX" <alvinx.zhang@intel.com>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>,
"Xing, Beilei" <beilei.xing@intel.com>,
"Guo, Junfeng" <junfeng.guo@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH] net/i40e: fix IPv6 fragment RSS offload type in flow
Date: Tue, 19 Oct 2021 01:51:53 +0000 [thread overview]
Message-ID: <14ef4f22b4124882b06751597983f8bc@intel.com> (raw)
In-Reply-To: <DM6PR11MB38980967486D92BFEC8B537C9FBD9@DM6PR11MB3898.namprd11.prod.outlook.com>
> -----Original Message-----
> From: Zhang, AlvinX <alvinx.zhang@intel.com>
> Sent: Tuesday, October 19, 2021 9:32 AM
> To: Zhang, Qi Z <qi.z.zhang@intel.com>; Yigit, Ferruh <ferruh.yigit@intel.com>;
> Xing, Beilei <beilei.xing@intel.com>; Guo, Junfeng <junfeng.guo@intel.com>
> Cc: dev@dpdk.org; stable@dpdk.org
> Subject: RE: [dpdk-stable] [PATCH] net/i40e: fix IPv6 fragment RSS offload type
> in flow
>
> > -----Original Message-----
> > From: Zhang, Qi Z <qi.z.zhang@intel.com>
> > Sent: Tuesday, October 19, 2021 8:03 AM
> > To: Yigit, Ferruh <ferruh.yigit@intel.com>; Zhang, AlvinX
> > <alvinx.zhang@intel.com>; Xing, Beilei <beilei.xing@intel.com>; Guo,
> > Junfeng <junfeng.guo@intel.com>
> > Cc: dev@dpdk.org; stable@dpdk.org
> > Subject: RE: [dpdk-stable] [PATCH] net/i40e: fix IPv6 fragment RSS
> > offload type in flow
> >
> >
> >
> > > -----Original Message-----
> > > From: Yigit, Ferruh <ferruh.yigit@intel.com>
> > > Sent: Saturday, October 16, 2021 4:50 AM
> > > To: Zhang, AlvinX <alvinx.zhang@intel.com>; Xing, Beilei
> > > <beilei.xing@intel.com>; Guo, Junfeng <junfeng.guo@intel.com>
> > > Cc: dev@dpdk.org; stable@dpdk.org; Zhang, Qi Z
> > > <qi.z.zhang@intel.com>
> > > Subject: Re: [dpdk-stable] [PATCH] net/i40e: fix IPv6 fragment RSS
> > > offload type in flow
> > >
> > > On 10/12/2021 9:39 AM, Alvin Zhang wrote:
> > > > To keep flow format uniform with ice, this patch adds support for
> > > > this RSS rule:
> > > > flow create 0 ingress pattern eth / ipv6_frag_ext / end actions \
> > > > rss types ipv6-frag end queues end queues end / end
> > > >
> > > > Fixes: ef4c16fd9148 ("net/i40e: refactor RSS flow")
> > > > Cc: stable@dpdk.org
> > > >
> > > > Signed-off-by: Alvin Zhang <alvinx.zhang@intel.com>
> > >
> > > './devtools/check-doc-vs-code.sh' script is failing [1], can you please fix it?
> > >
> > > [1]
> > > $ ./devtools/check-doc-vs-code.sh
> > > rte_flow doc out of sync for i40e
> > > item ipv6_frag_ext
> >
> >
> > Fixed in dpdk-next-net-intel.
> >
> > Thanks
> > Qi
>
> Hi Qi,
>
> I have found a issue for this patch, the pattern supported in ice is:
> eth / ipv6 / ipv6_frag_ext
>
> not
> eth / ipv6_frag_ext
>
> I will submit V2 today.
>
Ok, patch has been dropped from dpdk-next-net-intel.
next prev parent reply other threads:[~2021-10-19 1:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-12 8:39 [dpdk-dev] " Alvin Zhang
2021-10-15 9:36 ` Jiang, YuX
2021-10-15 13:45 ` Zhang, Qi Z
2021-10-15 20:50 ` [dpdk-dev] [dpdk-stable] " Ferruh Yigit
2021-10-19 0:03 ` Zhang, Qi Z
2021-10-19 1:31 ` Zhang, AlvinX
2021-10-19 1:51 ` Zhang, Qi Z [this message]
2021-10-19 1:53 ` [dpdk-dev] [PATCH v2] " Alvin Zhang
2021-10-19 11:05 ` 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=14ef4f22b4124882b06751597983f8bc@intel.com \
--to=qi.z.zhang@intel.com \
--cc=alvinx.zhang@intel.com \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=junfeng.guo@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).