From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: "Yan, Zhirun" <zhirun.yan@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"Yang, Qiming" <qiming.yang@intel.com>
Cc: "Wang, Xiao W" <xiao.w.wang@intel.com>
Subject: RE: [PATCH v1 1/3] net/ice/base: extend VXLAN type with inner pattern for FDIR
Date: Wed, 26 Apr 2023 08:17:58 +0000 [thread overview]
Message-ID: <DM4PR11MB59944933E549B920A9C25773D7659@DM4PR11MB5994.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20220622030032.474770-2-zhirun.yan@intel.com>
> -----Original Message-----
> From: Yan, Zhirun <zhirun.yan@intel.com>
> Sent: Wednesday, June 22, 2022 11:01 AM
> To: dev@dpdk.org; Zhang, Qi Z <qi.z.zhang@intel.com>; Yang, Qiming
> <qiming.yang@intel.com>
> Cc: Wang, Xiao W <xiao.w.wang@intel.com>; Yan, Zhirun
> <zhirun.yan@intel.com>
> Subject: [PATCH v1 1/3] net/ice/base: extend VXLAN type with inner pattern
> for FDIR
>
> When offload VXLAN rule only with inner IPv4 layer, we expect to hit a group
> flow include UDP/TCP/SCTP. The dummy packet of this flow type is specified
> with inner UDP type. This patch changed the inner IPv4 protocol type to a
> reserved value, then it could cover the inner UDP/TCP/SCTP.
>
> Signed-off-by: Zhirun Yan <zhirun.yan@intel.com>
Acked-by: Qi Zhang <qi.z.zhang@intel.com>
Applied to dpdk-next-net-intel.
Thanks
Qi
next prev parent reply other threads:[~2023-04-26 8:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-22 3:00 [PATCH v1 0/3] fix tunnel support for VXLAN in FDIR Zhirun Yan
2022-06-22 3:00 ` [PATCH v1 1/3] net/ice/base: extend VXLAN type with inner pattern for FDIR Zhirun Yan
2023-04-26 8:17 ` Zhang, Qi Z [this message]
2022-06-22 3:00 ` [PATCH v1 2/3] net/ice: fix outer src mac as FDIR input field Zhirun Yan
2023-04-26 8:15 ` Zhang, Qi Z
2022-06-22 3:00 ` [PATCH v1 3/3] net/ice: fix flow management in FDIR Zhirun Yan
2023-04-26 8:13 ` 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=DM4PR11MB59944933E549B920A9C25773D7659@DM4PR11MB5994.namprd11.prod.outlook.com \
--to=qi.z.zhang@intel.com \
--cc=dev@dpdk.org \
--cc=qiming.yang@intel.com \
--cc=xiao.w.wang@intel.com \
--cc=zhirun.yan@intel.com \
/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).