DPDK usage discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: Carlos de Souza Moraes Neto <carlosmn@weg.net>,
	Bruce Richardson <bruce.richardson@intel.com>,
	 Vladimir Medvedkin <vladimir.medvedkin@intel.com>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: [E810 Offload VLAN Stripping]
Date: Mon, 11 Mar 2024 16:11:14 +0100	[thread overview]
Message-ID: <CAJFAV8yadFAQFHoZgsgr3n6iO3bA1-NuEsbCADV5_-zxbHcftQ@mail.gmail.com> (raw)
In-Reply-To: <RO2P152MB600805BC21EC4774F7626A0EDD272@RO2P152MB6008.LAMP152.PROD.OUTLOOK.COM>

Hello Carlos,

On Mon, Mar 11, 2024 at 10:29 AM Carlos de Souza Moraes Neto
<carlosmn@weg.net> wrote:
> Hello,
>

Adding some Intel folks.

> I'm currently working on enabling the RTE_ETH_RX_OFFLOAD_VLAN_STRIP offload feature to strip VLAN tags and store the VLAN information in the vlan_tci field while using an Intel E810-XXVDA2 NIC. However, the VLAN tags are not being stripped. I’ve already tried to update DPDK (23.11), E810 firmware (4.40), ICE and DDP (1.3.35.0) but nothing. My console output is:
>
> EAL: Detected CPU lcores: 8
> EAL: Detected NUMA nodes: 1
> EAL: Detected shared linkage of DPDK
> EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
> EAL: Selected IOVA mode 'VA'
> EAL: VFIO support initialized
> EAL: Using IOMMU type 1 (Type 1)
> EAL: Probe PCI driver: net_ice (8086:159b) device: 0000:01:00.0 (socket -1)
> ice_load_pkg_type(): Active package is: 1.3.35.0, ICE OS Default Package (single VLAN mode)
> EAL: Probe PCI driver: net_ice (8086:159b) device: 0000:01:00.1 (socket -1)
> ice_load_pkg_type(): Active package is: 1.3.35.0, ICE OS Default Package (single VLAN mode)
> EAL: Probe PCI driver: net_e1000_igb (8086:1521) device: 0000:02:00.0 (socket -1)
> EAL: Probe PCI driver: net_e1000_igb (8086:1521) device: 0000:02:00.1 (socket -1)
> EAL: Probe PCI driver: net_e1000_igb (8086:1521) device: 0000:02:00.2 (socket -1)
> EAL: Probe PCI driver: net_e1000_igb (8086:1521) device: 0000:02:00.3 (socket -1)
> TELEMETRY: No legacy callbacks, legacy socket not created
> ice_set_rx_function(): Using AVX2 OFFLOAD Vector Rx (port 0).
> ice_set_tx_function(): Using AVX2 OFFLOAD Vector Tx (port 0).
> ice_vsi_config_outer_vlan_stripping(): Single VLAN mode (SVM) does not support qinq
> ice_set_rx_function(): Using AVX2 OFFLOAD Vector Rx (port 1).
> ice_set_tx_function(): Using AVX2 OFFLOAD Vector Tx (port 1).
> ice_vsi_config_outer_vlan_stripping(): Single VLAN mode (SVM) does not support qinq

I think I reproduce your issue (though I see messages claiming support
for double VLAN in my setup).

I tested with testpmd in v23.11 and a E810 nic:
04:00.0 Ethernet controller: Intel Corporation Ethernet Controller
E810-XXV for SFP (rev 02)

# ./build/app/dpdk-testpmd -a 0000:04:00.0 -- --enable-hw-vlan-strip -i
...
ice_load_pkg_type(): Active package is: 1.3.30.0, ICE OS Default
Package (double VLAN mode)
...
testpmd> set verbose 1
Change verbose level from 0 to 1
testpmd> start
...
port 0/queue 0: received 1 packets
  src=00:00:00:00:00:00 - dst=FF:FF:FF:FF:FF:FF - pool=mb_pool_0 -
type=0x8100 - length=60 - nb_segs=1 - hw ptype: L2_ETHER
L3_IPV4_EXT_UNKNOWN L4_NONFRAG  - sw ptype: L2_ETHER_VLAN L3_IPV4  -
l2_len=18 - l3_len=20 - Receive queue=0x0
  ol_flags: RTE_MBUF_F_RX_L4_CKSUM_GOOD RTE_MBUF_F_RX_IP_CKSUM_GOOD
RTE_MBUF_F_RX_OUTER_L4_CKSUM_GOOD


I did a bisect, v22.11 worked for me and I ended up on: de5da9d16430
("net/ice: support double VLAN") as the first bad commit.

Reverting it restores vlan stripping for me on RHEL9.

port 0/queue 0: received 1 packets
  src=00:00:00:00:00:00 - dst=FF:FF:FF:FF:FF:FF - pool=mb_pool_0 -
type=0x0800 - length=60 - nb_segs=1 - VLAN tci=0x2a - hw ptype:
L2_ETHER L3_IPV4_EXT_UNKNOWN L4_NONFRAG  - sw ptype: L2_ETHER L3_IPV4
- l2_len=14 - l3_len=20 - Receive queue=0x0
  ol_flags: RTE_MBUF_F_RX_VLAN RTE_MBUF_F_RX_L4_CKSUM_GOOD
RTE_MBUF_F_RX_IP_CKSUM_GOOD RTE_MBUF_F_RX_VLAN_STRIPPED
RTE_MBUF_F_RX_OUTER_L4_CKSUM_GOOD

Carlos, do you see the same?

Bruce, Vladimir, could you have a look and confirm on your side?


Thanks!

-- 
David Marchand


  reply	other threads:[~2024-03-11 15:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-08 18:18 Carlos de Souza Moraes Neto
2024-03-11 15:11 ` David Marchand [this message]
2024-03-11 18:06   ` RES: " Carlos de Souza Moraes Neto
2024-03-12 11:52     ` David Marchand
2024-03-12 20:10       ` RES: " Carlos de Souza Moraes Neto
2024-03-14 11:21         ` David Marchand

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=CAJFAV8yadFAQFHoZgsgr3n6iO3bA1-NuEsbCADV5_-zxbHcftQ@mail.gmail.com \
    --to=david.marchand@redhat.com \
    --cc=bruce.richardson@intel.com \
    --cc=carlosmn@weg.net \
    --cc=users@dpdk.org \
    --cc=vladimir.medvedkin@intel.com \
    /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).