From: Harrish SJ <harrish@aviznetworks.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: users@dpdk.org
Subject: Re: Reg Packet Type Issue in Intel X710 NIC
Date: Mon, 16 Oct 2023 22:55:39 +0530 [thread overview]
Message-ID: <DA911965-D2DB-424E-A712-7A6DEC020509@aviznetworks.com> (raw)
In-Reply-To: <20231016102354.6d77eeea@hermes.local>
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
> On 16-Oct-2023, at 10:53 PM, Stephen Hemminger <stephen@networkplumber.org> wrote:
>
> On Mon, 16 Oct 2023 22:47:18 +0530
> Harrish SJ <harrish@aviznetworks.com> wrote:
>
>> Hi Team,
>>
>> We are observing below issues w.r.t Packet types in Intel X710 NIC
>>
>> NIC Details: (from dpdk-devbind -s)
>> Network devices using DPDK-compatible driver
>> ============================================
>> 0000:81:00.1 'Ethernet Controller X710 for 10GbE SFP+ 1572' drv=igb_uio unused=i40e,vfio-pci,uio_pci_generic
>> 0000:82:00.1 'Ethernet Controller X710 for 10GbE SFP+ 1572' drv=igb_uio unused=i40e,vfio-pci,uio_pci_generic
>>
>> Packet type is not set as L2_ETHER_VLAN and only set as L2_ETHER when the packet is received as VLAN tagged.
>> IP Packet type is set as L3_IPV4_EXT_UNKNOWN for IP/IP+UDP packets - Is this expected.?
>> Packet type is set as UNKNOWN for GTP packets even after configuring DDP profile for the ports used.
>>
>> testpmd> ddp get list 0
>> Profile number is: 1
>>
>> Profile 0:
>> Track id: 0x80000008
>> Version: 1.0.4.0
>> Profile name: GTPv1-C/U IPv4/IPv6 payload
>>
>> Could you please help us in resolving/providing your inputs on the above issues observed.?
>> Thanks in advance,
>>
>> Regards and Thanks,
>> Harrish.S.J
>>
>
> Since in most cases VLAN is offloaded in mbuf and RTE_MBUF_F_RX_VLAN_STRIPPED is set
> in offload flags. If VLAN is stripped it makes sense that the packet type could just
> be L2_ETHER but it looks like it maybe driver dependent which is not good.
next prev parent reply other threads:[~2023-10-16 17:25 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 [this message]
2023-10-16 17:30 ` Stephen Hemminger
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=DA911965-D2DB-424E-A712-7A6DEC020509@aviznetworks.com \
--to=harrish@aviznetworks.com \
--cc=stephen@networkplumber.org \
--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).