From: ѽ҉ᶬḳ℠ <vtol@gmx.net>
To: netdev@vger.kernel.org
Subject: [DSA] L2 Forwarding Offload not working
Date: Thu, 9 Jul 2020 11:32:00 +0000 [thread overview]
Message-ID: <29a9c85b-8f5a-2b85-2c7d-9b7ca0a6cb41@gmx.net> (raw)
"kernel":"5.4.50", "system":"ARMv7 Processor rev 1
(v7l)","model":"Turris
Omnia","board_name":"cznic,turris-omnia","release":{"distribution":"OpenWrt","version":"SNAPSHOT","revision":"r13719-66e04abbb6","target":"mvebu/cortexa9","}
CPU Marvell Armada 385 88F6820 | Switch Marvell 88E6176
soft bridge br-lan enslaving DSA ports lan0 lan1 lan2
DSA master device eth1 (subsequent ip l exhibits slaves as lanX@eth1)
----------
After perusal of
https://www.kernel.org/doc/Documentation/networking/switchdev.txt it is
my understanding that offloading works only for static FDB entries,
though not clear to me:
* what the logic is behind, and
* why DSA ports are not static FDB entries by default (would only seem
logical)
That said queried bridge fdb for lan2 (as example here), producing:
44:8a:5b:47:0b:c2 dev lan2 master br-lan
44:8a:5b:47:0b:c2 dev lan2 vlan 1 self
then went ahead with
bridge fdb add 44:8a:5b:47:0b:c2 dev lan2 vlan 1 self
resulting in
44:8a:5b:47:0b:c2 dev lan2 master br-lan
44:8a:5b:47:0b:c2 dev lan2 vlan 1 self static
So it is static now but nothing about offload still. Next up
ip l s br-lan ty bridge vlan_filtering 1
checking again bridge fdb and now exhibiting
44:8a:5b:47:0b:c2 dev lan2 vlan 1 master br-lan
44:8a:5b:47:0b:c2 dev lan2 master br-lan
44:8a:5b:47:0b:c2 dev lan2 vlan 1 self static
Do I suffer some sort of misconception of how to get it working, missing
something?
next reply other threads:[~2020-07-09 11:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-09 11:32 ѽ҉ᶬḳ℠ [this message]
2020-07-09 13:53 ` [DSA] L2 Forwarding Offload not working Andrew Lunn
2020-07-09 14:06 ` ѽ҉ᶬḳ℠
2020-07-09 14:35 ` Andrew Lunn
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=29a9c85b-8f5a-2b85-2c7d-9b7ca0a6cb41@gmx.net \
--to=vtol@gmx.net \
--cc=netdev@vger.kernel.org \
/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.