From: "Xu, Ting" <ting.xu@intel.com>
To: "Guo, Junfeng" <junfeng.guo@intel.com>,
"Zhang, Qi Z" <qi.z.zhang@intel.com>,
"Yang, Qiming" <qiming.yang@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "stable@dpdk.org" <stable@dpdk.org>
Subject: RE: [PATCH 0/2] fix variable type in pattern parsing for raw flow
Date: Thu, 15 Jun 2023 05:23:50 +0000 [thread overview]
Message-ID: <BL0PR11MB3250BF024421CCE5680184DFF85BA@BL0PR11MB3250.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20230615051717.2906443-1-junfeng.guo@intel.com>
> -----Original Message-----
> From: Guo, Junfeng <junfeng.guo@intel.com>
> Sent: Thursday, June 15, 2023 1:17 PM
> To: Zhang, Qi Z <qi.z.zhang@intel.com>; Yang, Qiming
> <qiming.yang@intel.com>
> Cc: dev@dpdk.org; stable@dpdk.org; Xu, Ting <ting.xu@intel.com>; Guo,
> Junfeng <junfeng.guo@intel.com>
> Subject: [PATCH 0/2] fix variable type in pattern parsing for raw flow
>
> In current pattern parsing function for protocol agnostic flow offloading (raw
> flow), some of the variables of packet length are defined as uint8_t, which
> are too small for some large-size packets, such as srv6 (Segment Routing over
> IPv6 dataplane) type. Change the type to uint16_t.
>
> For example, the length of below srv6 paket is 268 B, larger than the max of
> uint8_t type (i.e., 256).
> "mac()/ipv6(nextheader=43)/ipv6srh(headerextlength=4,nextheader=41)\
> /ipv6(dst=2001:2:0:0:0:0:0:2)"
>
> Junfeng Guo (2):
> net/ice: fix variable type in pattern parsing for raw flow
> net/iavf: fix variable type in pattern parsing for raw flow
>
> drivers/net/iavf/iavf_hash.c | 2 +-
> drivers/net/ice/ice_fdir_filter.c | 2 +-
> drivers/net/ice/ice_hash.c | 2 +-
> 3 files changed, 3 insertions(+), 3 deletions(-)
>
> --
> 2.25.1
Acked-by: Ting Xu <ting.xu@intel.com>
next prev parent reply other threads:[~2023-06-15 5:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-15 5:17 Junfeng Guo
2023-06-15 5:17 ` [PATCH 1/2] net/ice: " Junfeng Guo
2023-06-15 5:17 ` [PATCH 2/2] net/iavf: " Junfeng Guo
2023-06-15 5:23 ` Xu, Ting [this message]
2023-06-15 7:28 ` [PATCH 0/2] " David Marchand
2023-06-16 5:48 ` Zhang, Qi Z
2023-06-16 6:22 ` Guo, Junfeng
2023-06-19 0:57 ` 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=BL0PR11MB3250BF024421CCE5680184DFF85BA@BL0PR11MB3250.namprd11.prod.outlook.com \
--to=ting.xu@intel.com \
--cc=dev@dpdk.org \
--cc=junfeng.guo@intel.com \
--cc=qi.z.zhang@intel.com \
--cc=qiming.yang@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).