diff options
author | David S. Miller <davem@davemloft.net> | 2022-04-20 10:34:34 +0100 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2022-04-20 10:34:34 +0100 |
commit | 8ab38ed779857fd6d739dacac928dd8df82c4655 (patch) | |
tree | 44cf842cc4876763af1b5c44cb9c15a35b75de46 /drivers/net | |
parent | cc4bdef26ecd56de16a04bc6d99aa10ff9076498 (diff) | |
parent | be6ff9665d642d4cd0800b508ded289eaa5b02a2 (diff) | |
download | linux-stable-8ab38ed779857fd6d739dacac928dd8df82c4655.tar.gz linux-stable-8ab38ed779857fd6d739dacac928dd8df82c4655.tar.bz2 linux-stable-8ab38ed779857fd6d739dacac928dd8df82c4655.zip |
Merge branch 'dsa-cross-chip-notifier-cleanup'
Vladimir Oltean says:
====================
DSA cross-chip notifier cleanups
This patch set makes the following improvements:
- Cross-chip notifiers pass a switch index, port index, sometimes tree
index, all as integers. Sometimes we need to recover the struct
dsa_port based on those integers. That recovery involves traversing a
list. By passing directly a pointer to the struct dsa_port we can
avoid that, and the indices passed previously can still be obtained
from the passed struct dsa_port.
- Resetting VLAN filtering on a switch has explicit code to make it run
on a single switch, so it has no place to stay in the cross-chip
notifier code. Move it out.
- Changing the MTU on a user port affects only that single port, yet the
code passes through the cross-chip notifier layer where all switches
are notified. Avoid that.
- Other related cosmetic changes in the MTU changing procedure.
Apart from the slight improvement in performance given by
(a) doing less work in cross-chip notifiers
(b) emitting less cross-chip notifiers
we also end up with about 100 less lines of code.
====================
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/net')
0 files changed, 0 insertions, 0 deletions