<div dir="ltr">Hi Bruce, Morten,<div> </div><div>1 follow up question about vlan_filter which is tangentially related to the QinQ/VLAN stripping conversation.</div><div> </div><div>Dean has a testcase in the QinQ testsuite which is supposed to check the vlan_filter capability correctness when processing a packet with Tag 88a8 + Tag 8100. So, the test steps are like:</div><div> </div><div>1. Create 2 packets (for context, the Dot1AD just means 88a8)</div><div> packets = [ Ether(dst="00:11:22:33:44:55", src="66:77:88:99:aa:bb") / Dot1AD(vlan=100) / Dot1Q(vlan=200) / IP(dst="192.0.2.1", src="198.51.100.1") / UDP(dport=1234, sport=5678) / Raw(b"xxxxx"), Ether(dst="00:11:22:33:44:55", src="66:77:88:99:aa:bb") / Dot1AD(vlan=101) / Dot1Q(vlan=200) / IP(dst="192.0.2.1", src="198.51.100.1") / UDP(dport=1234, sport=5678) / Raw(b"xxxxx"), ] 2. enable vlan filter on testpmd port 0, set port 0 rx_vlan to 100</div><div>3. Transmit the 2 packets above from TG to testpmd on the SUT. The first packet should be accepted, the second should be dropped. </div><div> </div><div>What he is seeing is that (at least with an ice e810 card) both packets are dropped. So, clearly the vlan_filter capability does not apply to 88a8 + Tag 8100 packets in DPDK (at least right now). We were curious if DPDK was skipping past the Dot1AD and reading the Dot1Q for the vlan_filter operation, but it is not, as even when rx_vlan on testpmd is set to 200, both packets are dropped.</div><div> </div><div>The vlan_filter capability description from the docs (pasted below) is not very verbose, so we can't tell whether it (should) apply to 88a8 packets or not. In any case, I think we will remove this testcase from the testsuite at least for this DPDK release (that will mean the testsuite just covers QinQ_strip, vlan_strip, and how DPDK reads the tags) which are the parts we are confident we are validating "correctly." But, I wanted to mention this so the question of what is the correct vlan_filter action for these packets is not lost. cheers.</div><div> --------- </div><div>2.27. VLAN filter Supports filtering of a VLAN Tag identifier. [uses] rte_eth_rxconf,rte_eth_rxmode: offloads:DEV_RX_OFFLOAD_VLAN_FILTER. [implements] eth_dev_ops: vlan_filter_set. [related] API: rte_eth_dev_vlan_filter().</div><div> </div><div> </div><div> </div><div> </div></div> <div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Fri, Aug 8, 2025 at 12:15 PM Bruce Richardson <<a href="mailto:bruce.richardson@intel.com">bruce.richardson@intel.com</a>> wrote: </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">The behaviour of VLAN tag stripping Rx offloads is unclear in DPDK, and not very well documented. Even the documentation that does exist appears contradictory. For example, the doxygen docs for the mbuf flag RTE_MBUF_F_RX_QINQ_STRIPPED says: "If RTE_MBUF_F_RX_QINQ_STRIPPED is set and RTE_MBUF_F_RX_VLAN_STRIPPED is unset, only the outer VLAN is removed from packet data,..." but the docs for RTE_MBUF_F_RX_QINQ says: "If the flag RTE_MBUF_F_RX_QINQ_STRIPPED is also present, both VLANs headers have been stripped from mbuf data, ..." Without a good definition of what the correct behaviour is, it's not possible to assess and ensure conformance across drivers. Update the documentation for NIC features, ethdev and mbuf library to all report the same information. - VLAN strip implies stripping a single/outer tag of type 0x8100 - QinQ strip implies stripping a single/outer tag of type 0x88a8, which may be followed by a tag of 0x8100. That inner tag is stripped if-and-only-if VLAN stripping is enabled too. Signed-off-by: Bruce Richardson <<a href="mailto:bruce.richardson@intel.com" target="_blank">bruce.richardson@intel.com</a>> --- V2: updated and reworded following discussion on RFC patch --- doc/guides/nics/features.rst | 31 +++++++++++++++++++++++++++++++ lib/ethdev/rte_ethdev.h | 28 ++++++++++++++++++++++++++++ lib/mbuf/rte_mbuf_core.h | 32 ++++++++++++++++++-------------- 3 files changed, 77 insertions(+), 14 deletions(-) diff --git a/doc/guides/nics/features.rst b/doc/guides/nics/features.rst index a075c057ec..df0b7edee7 100644 --- a/doc/guides/nics/features.rst +++ b/doc/guides/nics/features.rst @@ -483,6 +483,11 @@ VLAN offload ------------ Supports VLAN offload to hardware. +This includes both VLAN stripping on Rx and VLAN insertion on Tx. + +On Rx, VLAN strip removes one VLAN tag (default ethertype=0x8100) if present. +If multiple VLAN tags are present, it strips the outer tag only. +The stripped VLAN TCI is saved in mbuf->vlan_tci. * **[uses] rte_eth_rxconf,rte_eth_rxmode**: ``offloads:RTE_ETH_RX_OFFLOAD_VLAN_STRIP,RTE_ETH_RX_OFFLOAD_VLAN_FILTER,RTE_ETH_RX_OFFLOAD_VLAN_EXTEND``. * **[uses] rte_eth_txconf,rte_eth_txmode**: ``offloads:RTE_ETH_TX_OFFLOAD_VLAN_INSERT``. @@ -501,6 +506,32 @@ QinQ offload ------------ Supports QinQ (queue in queue) offload. +This includes both QinQ stripping on Rx and QinQ insertion on Tx. + +On Rx, QinQ strip removes the outer QinQ tag (default ethertype=0x88a8) if present. +If multiple QinQ tags are present it only strips the outer tag. +The tag stripped is saved in mbuf->vlan_tci_outer. + +If an outer QinQ tag is stripped and if VLAN stripping is also enabled, +any inner VLAN tag (default ethertype=0x8100) is also stripped. +That tag is stored in mbuf->vlan_tci. + +Summary of VLAN and QinQ stripping behavior for some possible input traffic options: + ++----------------------+-----------------------+------------------------------+------------------------------+ +| Input Traffic | VLAN-strip on | QinQ strip on | Both on | ++======================+=======================+==============================+==============================+ +| Single Tag 0x8100 | Tag in vlan_tci | | Tag in vlan_tci | ++----------------------+-----------------------+------------------------------+------------------------------+ +| Single Tag 0x88a8 | | Tag in vlan_tci_outer | Tag in vlan_tci_outer | ++----------------------+-----------------------+------------------------------+------------------------------+ +| Tag 88a8 + Tag 8100 | | Outer tag in vlan_tci_outer | Outer tag in vlan_tci_outer | +| | | | | +| | | | Inner tag in vlan_tci | ++----------------------+-----------------------+------------------------------+------------------------------+ +| Double Tag 0x8100 | Outer tag in vlan_tci | | Outer tag in vlan_tci | ++----------------------+-----------------------+------------------------------+------------------------------+ + * **[uses] rte_eth_rxconf,rte_eth_rxmode**: ``offloads:RTE_ETH_RX_OFFLOAD_QINQ_STRIP``. * **[uses] rte_eth_txconf,rte_eth_txmode**: ``offloads:RTE_ETH_TX_OFFLOAD_QINQ_INSERT``. diff --git a/lib/ethdev/rte_ethdev.h b/lib/ethdev/rte_ethdev.h index f9fb6ae549..5e226ff1c9 100644 --- a/lib/ethdev/rte_ethdev.h +++ b/lib/ethdev/rte_ethdev.h @@ -1552,11 +1552,39 @@ struct rte_eth_conf { /** * Rx offload capabilities of a device. */ +/** + * VLAN strip offload. + * + * When enabled, strips one VLAN tag (ethtype=0x8100) if available. + * If multiple VLAN tags are present, it strips the outer tag. + * The stripped VLAN TCI is saved in mbuf->vlan_tci + * and @ref RTE_MBUF_F_RX_VLAN_STRIPPED flag is set. + * + * Note: if @ref RTE_ETH_RX_OFFLOAD_QINQ_STRIP is also enabled, + * the stripped tag may be an inner tag present after a QinQ tag (ethtype=0x88a8). + * In this case, both @ref RTE_MBUF_F_RX_QINQ_STRIPPED and + * @ref RTE_MBUF_F_RX_VLAN_STRIPPED flags will be set in the received mbuf. + */ #define RTE_ETH_RX_OFFLOAD_VLAN_STRIP RTE_BIT64(0) #define RTE_ETH_RX_OFFLOAD_IPV4_CKSUM RTE_BIT64(1) #define RTE_ETH_RX_OFFLOAD_UDP_CKSUM RTE_BIT64(2) #define RTE_ETH_RX_OFFLOAD_TCP_CKSUM RTE_BIT64(3) #define RTE_ETH_RX_OFFLOAD_TCP_LRO RTE_BIT64(4) +/** + * QinQ strip offload. + * + * When enabled, strips outer QinQ tag (ethtype=0x88a8) if present. + * The stripped QinQ tag is saved in mbuf field vlan_tci_outer + * and @ref RTE_MBUF_F_RX_QINQ_STRIPPED flag is set. + * + * If a QinQ tag is stripped and VLAN stripping is also enabled, + * any inner VLAN tag (ethtype=0x8100) is also stripped and + * stored in mbuf field vlan_tci, with the flag @ref RTE_MBUF_F_RX_VLAN_STRIPPED + * being set. + * + * @see RTE_ETH_RX_OFFLOAD_VLAN_STRIP, @see RTE_MBUF_F_RX_QINQ_STRIPPED, + * @see RTE_MBUF_F_RX_VLAN_STRIPPED + */ #define RTE_ETH_RX_OFFLOAD_QINQ_STRIP RTE_BIT64(5) #define RTE_ETH_RX_OFFLOAD_OUTER_IPV4_CKSUM RTE_BIT64(6) #define RTE_ETH_RX_OFFLOAD_MACSEC_STRIP RTE_BIT64(7) diff --git a/lib/mbuf/rte_mbuf_core.h b/lib/mbuf/rte_mbuf_core.h index a0df265b5d..824f11d438 100644 --- a/lib/mbuf/rte_mbuf_core.h +++ b/lib/mbuf/rte_mbuf_core.h @@ -44,7 +44,7 @@ extern "C" { /** * The RX packet is a 802.1q VLAN packet, and the tci has been * saved in mbuf->vlan_tci. - * If the flag RTE_MBUF_F_RX_VLAN_STRIPPED is also present, the VLAN + * If the flag @ref RTE_MBUF_F_RX_VLAN_STRIPPED is also present, the VLAN * header has been stripped from mbuf data, else it is still * present. */ @@ -66,7 +66,11 @@ extern "C" { * A vlan has been stripped by the hardware and its tci is saved in * mbuf->vlan_tci. This can only happen if vlan stripping is enabled * in the RX configuration of the PMD. - * When RTE_MBUF_F_RX_VLAN_STRIPPED is set, RTE_MBUF_F_RX_VLAN must also be set. + * When RTE_MBUF_F_RX_VLAN_STRIPPED is set, @ref RTE_MBUF_F_RX_VLAN must also be set. + * + * Note: When @ref RTE_MBUF_F_RX_QINQ_STRIPPED is also set, + * the stripped tag is an inner tag, rather than a single or outer tag. + * @see RTE_MBUF_F_RX_QINQ_STRIPPED for more information. */ #define RTE_MBUF_F_RX_VLAN_STRIPPED (1ULL << 6) @@ -113,19 +117,19 @@ extern "C" { #define RTE_MBUF_F_RX_FDIR_FLX (1ULL << 14) /** - * The outer VLAN has been stripped by the hardware and its TCI is + * The outer QinQ Tag (ethtype=0x88a8) has been stripped by the hardware and its TCI is * saved in mbuf->vlan_tci_outer. - * This can only happen if VLAN stripping is enabled in the Rx + * This can only happen if QinQ stripping is enabled in the Rx * configuration of the PMD. - * When RTE_MBUF_F_RX_QINQ_STRIPPED is set, the flags RTE_MBUF_F_RX_VLAN - * and RTE_MBUF_F_RX_QINQ must also be set. + * When RTE_MBUF_F_RX_QINQ_STRIPPED is set, the flag RTE_MBUF_F_RX_QINQ must also be set. * * - If both RTE_MBUF_F_RX_QINQ_STRIPPED and RTE_MBUF_F_RX_VLAN_STRIPPED are * set, the 2 VLANs have been stripped by the hardware and their TCIs are * saved in mbuf->vlan_tci (inner) and mbuf->vlan_tci_outer (outer). * - If RTE_MBUF_F_RX_QINQ_STRIPPED is set and RTE_MBUF_F_RX_VLAN_STRIPPED - * is unset, only the outer VLAN is removed from packet data, but both tci - * are saved in mbuf->vlan_tci (inner) and mbuf->vlan_tci_outer (outer). + * is unset, only the outer VLAN is removed from packet data and + * stored in mbuf->vlan_tci_outer. + * The contents of mbuf->vlan_tci are undefined in this case. */ #define RTE_MBUF_F_RX_QINQ_STRIPPED (1ULL << 15) @@ -149,12 +153,12 @@ extern "C" { #define RTE_MBUF_F_RX_SEC_OFFLOAD_FAILED (1ULL << 19) /** - * The RX packet is a double VLAN, and the outer tci has been - * saved in mbuf->vlan_tci_outer. If this flag is set, RTE_MBUF_F_RX_VLAN - * must also be set and the inner tci is saved in mbuf->vlan_tci. - * If the flag RTE_MBUF_F_RX_QINQ_STRIPPED is also present, both VLANs - * headers have been stripped from mbuf data, else they are still - * present. + * The RX packet is a QinQ packet, and the outer tci has been + * saved in mbuf->vlan_tci_outer. + * If the flag @ref RTE_MBUF_F_RX_QINQ_STRIPPED is also present, + * the QinQ tag has been stripped from mbuf data. + * + * @see RTE_MBUF_F_RX_QINQ_STRIPPED, @see RTE_MBUF_F_RX_VLAN, @see RTE_MBUF_F_RX_VLAN_STRIPPED */ #define RTE_MBUF_F_RX_QINQ (1ULL << 20) -- 2.48.1 </blockquote></div>