[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200709143533.GN928075@lunn.ch>
Date: Thu, 9 Jul 2020 16:35:33 +0200
From: Andrew Lunn <andrew@...n.ch>
To: ѽ҉ᶬḳ℠ <vtol@....net>
Cc: netdev@...r.kernel.org
Subject: Re: [DSA] L2 Forwarding Offload not working
> 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
Powered by blists - more mailing lists