From: Khadem Ullah <14pwcse1224@uetpeshawar.edu.pk>
To: huangdengdui <huangdengdui@huawei.com>
Cc: "Ivan Malov" <ivan.malov@arknetworks.am>,
dev@dpdk.org, andrew.rybchenko@oktetlabs.ru,
jasvinder.singh@intel.com, bruce.richardson@intel.com,
thomas@monjalon.net,
"Stephen Hemminger" <stephen@networkplumber.org>,
"Morten Brørup" <mb@smartsharesystems.com>
Subject: Re: [PATCH] net/rte_net: fix inner L2 length for tunneled Ethernet packets
Date: Mon, 11 Aug 2025 14:19:53 +0500 [thread overview]
Message-ID: <CA++2-x77urxvqQMJHFd2GWsbo_t05buoxc9nrWLhw3KQR1VKSQ@mail.gmail.com> (raw)
In-Reply-To: <605ede7c-2842-4c36-bcb4-f9a0e9c1ac1c@huawei.com>
[-- Attachment #1: Type: text/plain, Size: 461 bytes --]
Yes, that is correct. Please ack in case you agree!
On Thu, Aug 7, 2025 at 5:33 PM huangdengdui <huangdengdui@huawei.com> wrote:
>
>
> > When processing a tunnel packet, it is preferable for the inner_l2_len
> in rte_net_hdr_lens and the l2_len in the mbuf to have consistent meanings,
> as these two fields are typically used together.
> > Moreover, inner_l2_len should only include the length of the Ethernet
> header.
>
>
Regards,
Khadem
[-- Attachment #2: Type: text/html, Size: 825 bytes --]
next prev parent reply other threads:[~2025-08-11 9:20 UTC|newest]
Thread overview: 15+ 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-07 12:33 ` huangdengdui
2025-08-11 9:19 ` Khadem Ullah [this message]
2025-08-11 9:39 ` Andrew Rybchenko
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=CA++2-x77urxvqQMJHFd2GWsbo_t05buoxc9nrWLhw3KQR1VKSQ@mail.gmail.com \
--to=14pwcse1224@uetpeshawar.edu.pk \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=huangdengdui@huawei.com \
--cc=ivan.malov@arknetworks.am \
--cc=jasvinder.singh@intel.com \
--cc=mb@smartsharesystems.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).