From: Simon Horman <horms@kernel.org>
To: Aleksandr Loktionov <aleksandr.loktionov@intel.com>
Cc: intel-wired-lan@lists.osuosl.org, anthony.l.nguyen@intel.com,
netdev@vger.kernel.org
Subject: Re: [PATCH net-next v1 0/2] virtchnl/ice: add IEEE 802.1ah (0x88E7) VLAN ethertype support
Date: Thu, 19 Mar 2026 17:11:11 +0000 [thread overview]
Message-ID: <20260319171111.GM1753385@horms.kernel.org> (raw)
In-Reply-To: <20260318080737.3012293-1-aleksandr.loktionov@intel.com>
On Wed, Mar 18, 2026 at 09:07:34AM +0100, Aleksandr Loktionov wrote:
> IEEE 802.1ah (Provider Backbone Bridging) defines the Backbone Service
> Tag (B-TAG) with ethertype 0x88E7. In environments that combine Provider
> Backbone Bridging with virtualisation, VFs may receive or transmit frames
> carrying a B-TAG and need to install matching VLAN filters on the PF.
>
> The existing virtchnl VLAN v2 capability handshake (via
> VIRTCHNL_OP_GET_OFFLOAD_VLAN_V2_CAPS) has dedicated bitmask entries for
> each supported ethertype (0x8100, 0x88A8, 0x9100) but lacked one for
> 0x88E7, making it impossible for a VF driver to advertise or negotiate
> B-TAG support.
>
> This series adds the missing capability flag and wires up the three
> software-path checks in the ice PF driver that guard VLAN filter
> installation:
>
> Patch 1 adds VIRTCHNL_VLAN_ETHERTYPE_88E7 = BIT(3) to the shared
> virtchnl_vlan_support enum in include/linux/avf/virtchnl.h.
>
> Patch 2 updates ice's TC TPID validation, VSI VLAN filter validation,
> and the bidirectional virtchnl VLAN v2 translation functions to
> accept/translate ETH_P_8021AH (0x88E7).
>
> No hardware offload changes, no datapath modifications.
>
> Tested on E810 with an iavf VF requesting 0x88E7-tagged VLAN filters:
> Verified that a TC flower rule matching on VLAN TPID 0x88E7 is now
> accepted and offloaded by the driver without returning -EINVAL:
>
> tc qdisc add dev $VF clsact
> tc filter add dev $VF ingress protocol 802.1Q flower \
> vlan_ethtype 0x88e7 action pass
> # (previously: Error: Failed to offload TC filter - vlan_type was 0)
>
> Also verified VF transparent passthrough of triple-tagged frames with
> 0x88E7 as middle and innermost tag using scapy on a back-to-back E810
> pair (kernel 6.19.0-rc8+, FW 4.91, ICE Triple VLAN Comms DDP 1.3.88.88).
>
> Aleksandr Loktionov (2):
> virtchnl: add VIRTCHNL_VLAN_ETHERTYPE_88E7 support
> ice: add 0x88E7 handling to SW validation paths
For the series:
Reviewed-by: Simon Horman <horms@kernel.org>
prev parent reply other threads:[~2026-03-19 17:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-18 8:07 [PATCH net-next v1 0/2] virtchnl/ice: add IEEE 802.1ah (0x88E7) VLAN ethertype support Aleksandr Loktionov
2026-03-18 8:07 ` [PATCH net-next v1 1/2] virtchnl: add VIRTCHNL_VLAN_ETHERTYPE_88E7 support Aleksandr Loktionov
2026-03-18 8:07 ` [PATCH net-next v1 2/2] ice: add 0x88E7 handling to SW validation paths Aleksandr Loktionov
2026-03-19 17:11 ` Simon Horman [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=20260319171111.GM1753385@horms.kernel.org \
--to=horms@kernel.org \
--cc=aleksandr.loktionov@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=netdev@vger.kernel.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