From: Dengdui Huang <huangdengdui@huawei.com>
To: <dev@dpdk.org>
Cc: <thomas@monjalon.net>, <jasvinder.singh@intel.com>,
<stephen@networkplumber.org>, <aman.deep.singh@intel.com>,
<lihuisong@huawei.com>, <fengchengwen@huawei.com>,
<liuyonglong@huawei.com>
Subject: [PATCH 1/2] net: fix parse the tunnel length of tunnel with UDP
Date: Mon, 16 Jun 2025 16:27:01 +0800 [thread overview]
Message-ID: <20250616082702.3422034-2-huangdengdui@huawei.com> (raw)
In-Reply-To: <20250616082702.3422034-1-huangdengdui@huawei.com>
Currently, the tunnel length info is not available when
get the tunnel packet type with UDP port. This patch
adds the parsing of the tunnel length info.
Additionally, adding comments for the inner_l2_len field
and the tunnel_len field would help in understanding their.
Fixes: 64ed7f854cf4 ("net: add tunnel packet type parsing")
Cc: stable@dpdk.org
Signed-off-by: Dengdui Huang <huangdengdui@huawei.com>
---
lib/net/rte_net.c | 4 ++++
lib/net/rte_net.h | 2 ++
2 files changed, 6 insertions(+)
diff --git a/lib/net/rte_net.c b/lib/net/rte_net.c
index 098999e71e..44fb6c0f51 100644
--- a/lib/net/rte_net.c
+++ b/lib/net/rte_net.c
@@ -197,6 +197,7 @@ ptype_tunnel_with_udp(uint16_t *proto, const struct rte_mbuf *m,
switch (port_no) {
case RTE_VXLAN_DEFAULT_PORT: {
*off += sizeof(struct rte_vxlan_hdr);
+ hdr_lens->tunnel_len = sizeof(struct rte_vxlan_hdr);
hdr_lens->inner_l2_len = RTE_ETHER_VXLAN_HLEN;
*proto = RTE_VXLAN_GPE_TYPE_ETH; /* just for eth header parse. */
return RTE_PTYPE_TUNNEL_VXLAN;
@@ -208,6 +209,7 @@ ptype_tunnel_with_udp(uint16_t *proto, const struct rte_mbuf *m,
if (unlikely(vgh == NULL))
return 0;
*off += sizeof(struct rte_vxlan_gpe_hdr);
+ hdr_lens->tunnel_len = sizeof(struct rte_vxlan_gpe_hdr);
hdr_lens->inner_l2_len = RTE_ETHER_VXLAN_GPE_HLEN;
*proto = vgh->proto;
@@ -243,6 +245,7 @@ ptype_tunnel_with_udp(uint16_t *proto, const struct rte_mbuf *m,
}
*off += gtp_len;
hdr_lens->inner_l2_len = gtp_len + sizeof(struct rte_udp_hdr);
+ hdr_lens->tunnel_len = gtp_len;
if (port_no == RTE_GTPC_UDP_PORT)
return RTE_PTYPE_TUNNEL_GTPC;
else if (port_no == RTE_GTPU_UDP_PORT)
@@ -258,6 +261,7 @@ ptype_tunnel_with_udp(uint16_t *proto, const struct rte_mbuf *m,
return 0;
geneve_len = sizeof(*gnh) + gnh->opt_len * 4;
*off += geneve_len;
+ hdr_lens->tunnel_len = geneve_len;
hdr_lens->inner_l2_len = sizeof(struct rte_udp_hdr) + geneve_len;
*proto = gnh->proto;
if (gnh->proto == 0)
diff --git a/lib/net/rte_net.h b/lib/net/rte_net.h
index 40ad6a71a1..65d724b84b 100644
--- a/lib/net/rte_net.h
+++ b/lib/net/rte_net.h
@@ -19,9 +19,11 @@ extern "C" {
*/
struct rte_net_hdr_lens {
uint8_t l2_len;
+ /* Outer_L4_len + ... + inner L2_len for tunneling pkt. */
uint8_t inner_l2_len;
uint16_t l3_len;
uint16_t inner_l3_len;
+ /* Protocol header of tunnel packets */
uint16_t tunnel_len;
uint8_t l4_len;
uint8_t inner_l4_len;
--
2.33.0
next prev parent reply other threads:[~2025-06-16 8:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-16 8:27 [PATCH 0/2] fix parse tunnel packet ptyoe Dengdui Huang
2025-06-16 8:27 ` Dengdui Huang [this message]
2025-06-16 8:27 ` [PATCH 2/2] app/testpmd: fix obtain inner info of tunnel packet Dengdui Huang
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=20250616082702.3422034-2-huangdengdui@huawei.com \
--to=huangdengdui@huawei.com \
--cc=aman.deep.singh@intel.com \
--cc=dev@dpdk.org \
--cc=fengchengwen@huawei.com \
--cc=jasvinder.singh@intel.com \
--cc=lihuisong@huawei.com \
--cc=liuyonglong@huawei.com \
--cc=stephen@networkplumber.org \
--cc=thomas@monjalon.net \
/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).