From: Stephen Hemminger <stephen@networkplumber.org>
To: Jie Hai <haijie1@huawei.com>
Cc: <dev@dpdk.org>, <thomas@monjalon.net>, <ferruh.yigit@amd.com>,
<aman.deep.singh@intel.com>, <lihuisong@huawei.com>,
<fengchengwen@huawei.com>, <huangdengdui@huawei.com>
Subject: Re: [PATCH v3 1/2] net: add ptype parse for tunnel packets
Date: Fri, 14 Feb 2025 08:35:53 -0800 [thread overview]
Message-ID: <20250214083553.492ddbd7@hermes.local> (raw)
In-Reply-To: <20250214015638.29983-2-haijie1@huawei.com>
On Fri, 14 Feb 2025 09:56:37 +0800
Jie Hai <haijie1@huawei.com> wrote:
> Add packet types parse for vxlan/vxlan-gpe/gtp/geneve packets.
>
> Signed-off-by: Jie Hai <haijie1@huawei.com>
> ---
Not sure about this.
The original purpose of ptype was to support hardware offload information.
Does any driver do this ptype detection in tunnels?
Would the software detection produce the same result as HW offload?
next prev parent reply other threads:[~2025-02-14 16:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-08 2:46 [PATCH] app/testpmd: add ipv6 extension header parse Jie Hai
2025-01-08 17:02 ` Stephen Hemminger
2025-01-14 2:05 ` Jie Hai
2025-01-14 11:24 ` Thomas Monjalon
2025-01-24 9:43 ` [PATCH v2 0/2] parse ptype for tunnel packets Jie Hai
2025-01-24 9:43 ` [PATCH v2 1/2] net: add ptype parse " Jie Hai
2025-01-30 18:26 ` Stephen Hemminger
2025-01-24 9:43 ` [PATCH v2 2/2] app/test-pmd: use ptype API parse packets Jie Hai
2025-02-14 1:56 ` [PATCH v3 0/2] app/testpmd: add ipv6 extension header parse Jie Hai
2025-02-14 1:56 ` [PATCH v3 1/2] net: add ptype parse for tunnel packets Jie Hai
2025-02-14 16:35 ` Stephen Hemminger [this message]
2025-02-14 1:56 ` [PATCH v3 2/2] app/test-pmd: use ptype API parse packets Jie Hai
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=20250214083553.492ddbd7@hermes.local \
--to=stephen@networkplumber.org \
--cc=aman.deep.singh@intel.com \
--cc=dev@dpdk.org \
--cc=fengchengwen@huawei.com \
--cc=ferruh.yigit@amd.com \
--cc=haijie1@huawei.com \
--cc=huangdengdui@huawei.com \
--cc=lihuisong@huawei.com \
--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).