aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python
diff options
context:
space:
mode:
authorVladimir Oltean <[email protected]>2019-06-26 02:39:38 +0300
committerDavid S. Miller <[email protected]>2019-06-27 11:03:21 -0700
commit60f6053ff142217488d3f0d7b692f6a4ef45b99f (patch)
tree5614f882f20e7af24e88dc29f73dd7ab9dfa53d3 /tools/perf/scripts/python
parent6c56e167cc1b60f69a265ead1ef7f413f0e2ed64 (diff)
net: dsa: sja1105: Back up static FDB entries in kernel memory
After commit 8456721dd4ec ("net: dsa: sja1105: Add support for configuring address ageing time"), we started to reset the switch rather often (each time the bridge core changes the ageing time on a switch port). The unfortunate reality is that SJA1105 doesn't have any {cold, warm, whatever} reset mode in which it accepts a new configuration stream without flushing the FDB. Instead, in its world, the FDB *is* an optional part of the static configuration. So we play its game, and do what we also do for VLANs: for each 'bridge fdb' command, we add the FDB entry through the dynamic interface, and we append the in-kernel static config memory with info that we're going to use later, when the next reset command is going to be issued. The result is that 'bridge fdb' commands are now persistent (dynamically learned entries are lost, but that's ok). Signed-off-by: Vladimir Oltean <[email protected]> Signed-off-by: David S. Miller <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions