From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: "Yan, Zhirun" <zhirun.yan@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"Wang, Xiao W" <xiao.w.wang@intel.com>
Cc: "Cao, Yahui" <yahui.cao@intel.com>,
"Guo, Junfeng" <junfeng.guo@intel.com>,
"Xu, Ting" <ting.xu@intel.com>
Subject: Re: [dpdk-dev] [PATCH v3] net/ice: support VXLAN VNI field in FDIR
Date: Thu, 1 Apr 2021 12:10:49 +0000 [thread overview]
Message-ID: <473c393a0d3242b48ec1ff3a769f5b7a@intel.com> (raw)
In-Reply-To: <20210401013323.3186609-1-zhirun.yan@intel.com>
> -----Original Message-----
> From: Yan, Zhirun <zhirun.yan@intel.com>
> Sent: Thursday, April 1, 2021 9:33 AM
> To: dev@dpdk.org; Zhang, Qi Z <qi.z.zhang@intel.com>; Wang, Xiao W
> <xiao.w.wang@intel.com>
> Cc: Cao, Yahui <yahui.cao@intel.com>; Guo, Junfeng <junfeng.guo@intel.com>;
> Xu, Ting <ting.xu@intel.com>; Yan, Zhirun <zhirun.yan@intel.com>
> Subject: [PATCH v3] net/ice: support VXLAN VNI field in FDIR
>
> Add support for VNI field in FDIR. Treat VXLAN flow type as
> ICE_FLTR_PTYPE_NONF_IPV4_UDP_VXLAN to align with shared code. It allows
> to match outer L2/L3, VNI and inner L2/L3 fields with VXLAN pattern.
> VNI takes 24 bits in VXLAN header, but uses 32 bits for matching in shared
> code. The 8 bits reserved field adjacent should always be 0.
>
> 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
prev parent reply other threads:[~2021-04-01 12:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-24 8:25 [dpdk-dev] [PATCH v1] " Zhirun Yan
2021-04-01 1:33 ` [dpdk-dev] [PATCH v3] " Zhirun Yan
2021-04-01 12:10 ` Zhang, Qi Z [this message]
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=473c393a0d3242b48ec1ff3a769f5b7a@intel.com \
--to=qi.z.zhang@intel.com \
--cc=dev@dpdk.org \
--cc=junfeng.guo@intel.com \
--cc=ting.xu@intel.com \
--cc=xiao.w.wang@intel.com \
--cc=yahui.cao@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).