diff options
| author | Jakub Kicinski <kuba@kernel.org> | 2026-09-21 17:41:34 -0700 |
|---|---|---|
| committer | Jakub Kicinski <kuba@kernel.org> | 2026-09-21 17:41:35 -0700 |
| commit | 8cf9152d947c65f3243d4c0d8f98f0b52c4f0b9b (patch) | |
| tree | 3dd0597f8a61fdab74bea7f309df1765c4a494f7 /include/linux/debugobjects.h | |
| parent | bfc9df9e40c9a8562dabd5f2339787e63b75a325 (diff) | |
| parent | fee4e7663e5cdc19bfe1d26f0651f2f9e04922d7 (diff) | |
Merge branch 'net-bridge-vlan-broadcast-fwding-path-optimizations'
Nikolay Aleksandrov says:
====================
net: bridge: vlan: broadcast fwding path optimizations
This patch-set is the first step to removing unnecessary VLAN hash lookups
from the bridge fast-path and also provides additional broadcast path
optimization by considering only the port-VLANs that actually participate
in the VLAN instead of all bridge ports. Combined these changes bring
considerable improvements (see patch 8's commit message) and open
the path to do the same for the most common fdb forwarding path.
As expected the pathological cases have the largest gain,
e.g. if we have 1 client / VM facing port and 1 upstream port
only participating in a VLAN with many other bridge ports, we consider only
those 2 when broadcasting in that VLAN.
For up to 8 ports we only use the port-VLAN list as the array doesn't make
much of a difference and is unnecessary. Note that the array is rebuilt on
every member add or delete when >8 members, I tested that and could do
2000 VLAN add/delete with 64 port-VLAN members / sec on my test VM.
If it ever becomes a problem we can optimize it further, for the time
being I prefer it is simpler.
====================
Link: https://patch.msgid.link/20260918152950.1938259-1-razor@blackwall.org
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'include/linux/debugobjects.h')
0 files changed, 0 insertions, 0 deletions
