All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: ѽ҉ᶬḳ℠ <vtol@gmx.net>
Cc: netdev@vger.kernel.org
Subject: Re: [DSA] L2 Forwarding Offload not working
Date: Thu, 9 Jul 2020 16:35:33 +0200	[thread overview]
Message-ID: <20200709143533.GN928075@lunn.ch> (raw)
In-Reply-To: <50c35a41-45c2-1f2b-7189-96fe7c0a1740@gmx.net>

> 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

  reply	other threads:[~2020-07-09 14:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-09 11:32 [DSA] L2 Forwarding Offload not working ѽ҉ᶬḳ℠
2020-07-09 13:53 ` Andrew Lunn
2020-07-09 14:06   ` ѽ҉ᶬḳ℠
2020-07-09 14:35     ` Andrew Lunn [this message]
2020-07-09 14:57       ` ѽ҉ᶬḳ℠

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=20200709143533.GN928075@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=netdev@vger.kernel.org \
    --cc=vtol@gmx.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.