diff options
| author | David S. Miller <davem@davemloft.net> | 2018-04-01 05:19:14 +0300 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2018-04-01 05:19:14 +0300 |
| commit | 24197ee2102359b59044234347dd3504302fa97d (patch) | |
| tree | 3c81eed86eff79013e00169ac749661b7d6b4ca4 /net/tipc/subscr.h | |
| parent | 56c03cbf8c4cbd413a19e8541850b0f02958fdcb (diff) | |
| parent | 804b854d374e39f5f8bff9638fd274b9a9ca7d33 (diff) | |
Merge branch 'bridge-mtu'
Nikolay Aleksandrov says:
====================
net: bridge: MTU handling changes
As previously discussed the recent changes break some setups and could lead
to packet drops. Thus the first patch reverts the behaviour for the bridge
to follow the minimum MTU but also keeps the ability to set the MTU to the
maximum (out of all ports) if vlan filtering is enabled. Patch 02 is the
bigger change in behaviour - we've always had trouble when configuring
bridges and their MTU which is auto tuning on port events
(add/del/changemtu), which means config software needs to chase it and fix
it after each such event, after patch 02 we allow the user to configure any
MTU (ETH_MIN/MAX limited) but once that is done the bridge stops auto
tuning and relies on the user to keep the MTU correct.
This should be compatible with cases that don't touch the MTU (or set it
to the same value), while allowing to configure the MTU and not worry
about it changing afterwards.
The patches are intentionally split like this, so that if they get accepted
and there are any complaints patch 02 can be reverted.
====================
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/tipc/subscr.h')
0 files changed, 0 insertions, 0 deletions