[lkml]   [2021]   [Feb]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH v2 net-next 04/11] net: bridge: offload initial and final port flags through switchdev
    On Tue, Feb 09, 2021 at 08:51:00PM +0200, Ido Schimmel wrote:
    > On Tue, Feb 09, 2021 at 05:19:29PM +0200, Vladimir Oltean wrote:
    > > So switchdev drivers operating in standalone mode should disable address
    > > learning. As a matter of practicality, we can reduce code duplication in
    > > drivers by having the bridge notify through switchdev of the initial and
    > > final brport flags. Then, drivers can simply start up hardcoded for no
    > > address learning (similar to how they already start up hardcoded for no
    > > forwarding), then they only need to listen for
    > > SWITCHDEV_ATTR_ID_PORT_BRIDGE_FLAGS and their job is basically done, no
    > > need for special cases when the port joins or leaves the bridge etc.
    > How are you handling the case where a port leaves a LAG that is linked
    > to a bridge? In this case the port becomes a standalone port, but will
    > not get this notification.

    Apparently the answer to that question is "I delete the code that makes
    this use case work", how smart of me. Thanks.

    Unless you have any idea how I could move the logic into the bridge, I
    guess I'm stuck with DSA and all the other switchdev drivers having this
    forest of corner cases to deal with. At least I can add a comment so I'm
    not tempted to delete it next time.

     \ /
      Last update: 2021-02-10 01:26    [W:6.897 / U:1.056 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site