From: Stephen Hemminger <stephen@networkplumber.org>
To: Harrish SJ <harrish@aviznetworks.com>
Cc: users@dpdk.org
Subject: Re: Reg Packet Type Issue in Intel X710 NIC
Date: Mon, 16 Oct 2023 10:30:07 -0700 [thread overview]
Message-ID: <20231016103007.340048cb@hermes.local> (raw)
In-Reply-To: <DA911965-D2DB-424E-A712-7A6DEC020509@aviznetworks.com>
On Mon, 16 Oct 2023 22:55:39 +0530
Harrish SJ <harrish@aviznetworks.com> wrote:
> Thanks much Stephen for your inputs. Let me check the flags and get back.
> Any inputs on GTP Packet type as UNKNOWN would be much helpful.
> Thanks in advance,
>
> Regards and Thanks,
> Harrish.S.J
Packet type recognition in either done in software (slow) or hardware.
The hardware recognition is limited by what that NIC is able to recognize.
I suspect most NIC's just look at ether type and maybe IP proto fields
while processing packet.
In any case packet type is not very reliable across NIC vendors.
If you really want to identify packets either do it in SW or use
rte_flow if NIC supports it.
prev parent reply other threads:[~2023-10-16 17:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-16 17:17 Harrish SJ
2023-10-16 17:23 ` Stephen Hemminger
2023-10-16 17:25 ` Harrish SJ
2023-10-16 17:30 ` Stephen Hemminger [this message]
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=20231016103007.340048cb@hermes.local \
--to=stephen@networkplumber.org \
--cc=harrish@aviznetworks.com \
--cc=users@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).