On Tue, 19 Dec 2023, Vladimir Oltean wrote: > DSA_TAG_PROTO_LAN9303, DSA_TAG_PROTO_SJA1105 and DSA_TAG_PROTO_SJA1110 > construct tags with ETH_P_8021Q as EtherType. Do you still think it > would be correct to say that all DSA tags break COE on the stmmac, as > this patch assumes? > > The NETIF_F_IP_CSUM | NETIF_F_IPV6_CSUM convention is not about > statically checking whether the interface using DSA, but about looking > at each packet before deciding whether to use the offload engine or to > call skb_checksum_help(). > > You can experiment with any tagging protocol on the stmmac driver, and > thus with the controller's response to any kind of traffic, even if the > port is not attached to a hardware switch. You need to enable the Thanks for telling me about DSA_LOOP, I've tested several DSA tagging protocols with the RZN1 GMAC1 hardware using this method. Here's what I found in a nutshell: For tagging protocols that change the EtherType field in the MAC header (e.g. DSA_TAG_PROTO_(DSA/EDSA/BRCM/MTK/RTL4C_A/SJA1105): On TX the tagged frames are almost always ignored by the checksum offload engine and IP header checker of the MAC device. I say "almost always" because there is an unlikely but nasty corner case where a DSA tag can be identical to an IP EtherType value. In these cases, the frame will likely fail IP header checks and be dropped by the MAC. Ignoring these corner cases, the DSA frames will egress with a partial checksum and be dropped by the recipient. On RX, these frames will, once again, not be detected as IP frames by the MAC. So they will be transmitted to the CPU. However, the stmmac driver will assume (wrongly in this case) that these frames' checksums have been verified by the MAC. So it will set CHECKSUM_UNECESSARY: https://elixir.bootlin.com/linux/latest/source/drivers/net/ethernet/stmicro/stmmac/stmmac_main.c#L5493 And so the IP/TCP checksums will not be checked at all, which is not ideal. There are other DSA tagging protocols which cause different issues. For example DSA_TAG_PROTO_BRCM_PREPEND, which seems to offset the whole MAC header, and DSA_TAG_PROTO_LAN9303 which sets ETH_P_8021Q as its EtherType. I haven't dug too deeply on these issues yet, since I'd rather deal with the checksumming issue before getting distracted by VLAN offloading and other stuff. Among the tagging protocols I tested, the only one that didn't cause any issues was DSA_TAG_PROTO_TRAILER, which only appends stuff to the frame. TLDR: The simplest solution seems to be to modify the stmmac TX and RX paths to disable checksum offloading for frames that have a non-IP ethertype in their MAC header. This will fix the checksum situation for DSA tagging protocols that set non-IP and non-8021Q EtherTypes. Some edge cases like DSA_TAG_PROTO_BRCM_PREPEND and DSA_TAG_PROTO_LAN9303 will require a completely different solution if we want these MAC devices to handle them properly. Please share any thoughts you might have on this suggestion. Best Regards, -- Romain Gantois, Bootlin Embedded Linux and Kernel engineering https://bootlin.com
