From: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
To: Khadem Ullah <14pwcse1224@uetpeshawar.edu.pk>,
dev@dpdk.org, jasvinder.singh@intel.com,
bruce.richardson@intel.com
Cc: thomas@monjalon.net, ivan.malov@arknetworks.am, stable@dpdk.org
Subject: Re: [PATCH] net/rte_net: fix inner L2 length for tunneled Ethernet packets
Date: Mon, 11 Aug 2025 12:39:56 +0300 [thread overview]
Message-ID: <7416c5c9-7485-4de1-8006-78a6df128080@oktetlabs.ru> (raw)
In-Reply-To: <20250801112834.60310-1-14pwcse1224@uetpeshawar.edu.pk>
On 8/1/25 14:28, Khadem Ullah wrote:
> Hi Andrew,
>
> Thanks for your feedback.
>
> Please check mbuf packet types and the following test case:
> https://doc.dpdk.org/dts-20.02/test_plans/uni_pkt_test_plan.html#test-case-vxlan-tunnel-packet-type-detect
> sendp([Ether()/IP()/UDP()/Vxlan()/Ether()/IP(frag=5)/Raw('\0'*40)],
> iface=txItf)
>
> (outer) L2 type: ETHER
> (outer) L3 type: IPV4_EXT_UNKNOWN
> (outer) L4 type: Unknown
> Tunnel type: GRENAT
> Inner L2 type: ETHER
> Inner L3 type: IPV4_EXT_UNKNOWN
> Inner L4 type: L4_FRAG
>
>
> union {
> uint32_t packet_type; /**< L2/L3/L4 and tunnel information. */
> __extension__
> struct {
> uint8_t l2_type:4; /**< (Outer) L2 type. */
> uint8_t l3_type:4; /**< (Outer) L3 type. */
> uint8_t l4_type:4; /**< (Outer) L4 type. */
> uint8_t tun_type:4; /**< Tunnel type. */
> union {
> uint8_t inner_esp_next_proto;
> /**< ESP next protocol type, valid if
> * RTE_PTYPE_TUNNEL_ESP tunnel type is set
> * on both Tx and Rx.
> */
> __extension__
> struct {
> uint8_t inner_l2_type:4;
> /**< Inner L2 type. */
> uint8_t inner_l3_type:4;
> /**< Inner L3 type. */
> };
> };
> uint8_t inner_l4_type:4; /**< Inner L4 type. */
> };
> };
>
>
> Based on the above, it seems that inner_l2_len have to the length of Ether.
Why?
> Ther might need to be some correspondent between both fields to potray the same information.
> Or, the inner_l2_type and inner_l2_len are completly different ?
Definition says that it is different.
>
> Best Regards,
> Khadem
next prev parent reply other threads:[~2025-08-11 9:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-28 13:12 Khadem Ullah
2025-07-28 13:28 ` Ivan Malov
2025-07-29 5:06 ` Khadem Ullah
2025-07-31 10:26 ` Andrew Rybchenko
2025-08-01 11:28 ` Khadem Ullah
2025-08-01 13:23 ` Ivan Malov
2025-08-11 9:39 ` Andrew Rybchenko [this message]
2025-08-11 10:13 ` Khadem Ullah
2025-08-11 11:22 ` Andrew Rybchenko
2025-08-11 12:17 ` Khadem Ullah
2025-07-31 10:21 ` Andrew Rybchenko
-- strict thread matches above, loose matches on Subject: below --
2025-07-28 12:30 Khadem Ullah
2025-07-28 12:21 Khadem Ullah
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=7416c5c9-7485-4de1-8006-78a6df128080@oktetlabs.ru \
--to=andrew.rybchenko@oktetlabs.ru \
--cc=14pwcse1224@uetpeshawar.edu.pk \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=ivan.malov@arknetworks.am \
--cc=jasvinder.singh@intel.com \
--cc=stable@dpdk.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).