From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 1F043C433E0 for ; Thu, 9 Jul 2020 14:35:36 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 017B720767 for ; Thu, 9 Jul 2020 14:35:36 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726886AbgGIOff (ORCPT ); Thu, 9 Jul 2020 10:35:35 -0400 Received: from vps0.lunn.ch ([185.16.172.187]:55364 "EHLO vps0.lunn.ch" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726353AbgGIOff (ORCPT ); Thu, 9 Jul 2020 10:35:35 -0400 Received: from andrew by vps0.lunn.ch with local (Exim 4.94) (envelope-from ) id 1jtXe9-004LHE-5f; Thu, 09 Jul 2020 16:35:33 +0200 Date: Thu, 9 Jul 2020 16:35:33 +0200 From: Andrew Lunn To: =?utf-8?B?0b3SieG2rOG4s+KEoA==?= Cc: netdev@vger.kernel.org Subject: Re: [DSA] L2 Forwarding Offload not working Message-ID: <20200709143533.GN928075@lunn.ch> References: <29a9c85b-8f5a-2b85-2c7d-9b7ca0a6cb41@gmx.net> <20200709135335.GL928075@lunn.ch> <50c35a41-45c2-1f2b-7189-96fe7c0a1740@gmx.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <50c35a41-45c2-1f2b-7189-96fe7c0a1740@gmx.net> Sender: netdev-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org > Two questions if you do not mind: > > 1) does the above apply to all stable kernel releases or only => 5.4? > Because with 4.14 there are reports that dynamic addresses of clients > roaming from a switch port to an bridge port (upstream of the switch, > e.g. WLan AP provided by the router) facing time outs until the switch > retires (ages) the client's MAC. DSA has always worked like this. It does however very from switch to switch. When adding a new switch, the first version of the driver sometimes does not support offloading. All frames are forwarded to the software bridge, and the software bridge does all the work. Then the driver gets extended, to support the hardware doing the work. And the driver gets extended again to allow static FDB entries to be passed to the hardware. DSA drivers are not 'big bang'. It is not all or nothing. They gain features with time. So you need to look at the driver in your specific version of the kernel to see what it supports. And you might need to be careful with the OpenWRT kernel, see if they have backported features. > > 2) The document > https://www.kernel.org/doc/Documentation/networking/switchdev.txt cites > (for static entries) > > bridge command will label these entries "offload" > > Is that still up-to-date or rather outdated from the earlier days of DSA? It should be true. But you need a reasonably recent iproute2 for this to be shown. Andrew