diff options
| author | Thomas Nixon <tom@tomn.co.uk> | 2021-07-09 22:58:18 +0000 |
|---|---|---|
| committer | Hauke Mehrtens <hauke@hauke-m.de> | 2022-01-16 20:51:14 +0100 |
| commit | 255268ce1a218a670e653dc5c83067f704164b7c (patch) | |
| tree | c460ac7e5735dc241e508ad3abd214e6156540f7 /tools/mpfr | |
| parent | 607f06f81cc630448484800e47830fbf0cbc1e24 (diff) | |
| download | upstream-255268ce1a218a670e653dc5c83067f704164b7c.tar.gz upstream-255268ce1a218a670e653dc5c83067f704164b7c.tar.bz2 upstream-255268ce1a218a670e653dc5c83067f704164b7c.zip | |
lantiq: xrx200: enable use of baby jumbo frames
xrx200 max MTU is reduced so that it works correctly when set to the
max, and the max MTU of the switch is increased to match.
In 5.10, the switch driver now enables non-standard MTUs on a per-port
basis, with the overall frame size set based on the cpu port. When the
MTU is not used, this should have no effect. The maximum packet size is
limited as large packets cause the switch to lock up.
0702-net-lantiq-add-support-for-jumbo-frames.patch comes from net-next
commit 998ac358019e491217e752bc6dcbb3afb2a6fa3e.
In 5.4, all switch ports are configured to accept the max MTU, as 5.4
does not have port_max_mtu/port_change_mtu callbacks.
Signed-off-by: Thomas Nixon <tom@tomn.co.uk>
Diffstat (limited to 'tools/mpfr')
0 files changed, 0 insertions, 0 deletions