From: "Jiang, YuX" <yux.jiang@intel.com>
To: "Zhang, AlvinX" <alvinx.zhang@intel.com>,
"Xing, Beilei" <beilei.xing@intel.com>,
"Guo, Junfeng" <junfeng.guo@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"Zhang, AlvinX" <alvinx.zhang@intel.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH] net/i40e: fix IPv6 fragment RSS offload type in flow
Date: Fri, 15 Oct 2021 09:36:59 +0000 [thread overview]
Message-ID: <SJ0PR11MB5150121ABEB65E2FD2B8EC06FEB99@SJ0PR11MB5150.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20211012083932.1428-1-alvinx.zhang@intel.com>
> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of Alvin Zhang
> Sent: Tuesday, October 12, 2021 4:40 PM
> To: Xing, Beilei <beilei.xing@intel.com>; Guo, Junfeng
> <junfeng.guo@intel.com>
> Cc: dev@dpdk.org; Zhang, AlvinX <alvinx.zhang@intel.com>;
> stable@dpdk.org
> Subject: [dpdk-dev] [PATCH] net/i40e: fix IPv6 fragment RSS offload type in
> flow
>
> 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>
Tested-by: Yu Jiang <YuX.Jiang@intel.com>
next prev parent reply other threads:[~2021-10-15 9:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-12 8:39 [dpdk-stable] " Alvin Zhang
2021-10-15 9:36 ` Jiang, YuX [this message]
2021-10-15 13:45 ` [dpdk-stable] [dpdk-dev] " Zhang, Qi Z
2021-10-15 20:50 ` [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
2021-10-19 1:53 ` [dpdk-stable] [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=SJ0PR11MB5150121ABEB65E2FD2B8EC06FEB99@SJ0PR11MB5150.namprd11.prod.outlook.com \
--to=yux.jiang@intel.com \
--cc=alvinx.zhang@intel.com \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--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).