aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/generic/backport-5.10/738-v5.14-02-net-dsa-qca8k-check-the-correct-variable-in-qca8k-se.patch
diff options
context:
space:
mode:
authorRafał Miłecki <rafal@milecki.pl>2023-02-07 18:09:40 +0100
committerRafał Miłecki <rafal@milecki.pl>2023-07-10 13:31:08 +0200
commite17f9fd0e8a9d7fbe159495b142b3a890f69db3a (patch)
tree89172e0da1bd2562c4a841f1f7c208d6dea76122 /target/linux/generic/backport-5.10/738-v5.14-02-net-dsa-qca8k-check-the-correct-variable-in-qca8k-se.patch
parent80a6b0a9173a1182081e184fd0f22c0996bd16b2 (diff)
downloadupstream-e17f9fd0e8a9d7fbe159495b142b3a890f69db3a.tar.gz
upstream-e17f9fd0e8a9d7fbe159495b142b3a890f69db3a.tar.bz2
upstream-e17f9fd0e8a9d7fbe159495b142b3a890f69db3a.zip
bcm47xx: revert bgmac back to the old limited max frame size
Bumping max frame size has significantly affected network performance and memory usage. It was done by upstream commit that first appeared in the 5.7 release. Allocating 512 (BGMAC_RX_RING_SLOTS) buffers, 10 k each, is clearly a bad idea on 32 MiB devices. This commit fixes support for Linksys E1000 V2.1 which gives up after allocating ~346 such buffers running 5.15 kernel. Ref: 230c9da963aa ("bcm53xx: revert bgmac back to the old limited max frame size") Signed-off-by: Rafał Miłecki <rafal@milecki.pl> (cherry picked from commit 4970dd027bced78f8a72aa2baed22c962d3b587b)
Diffstat (limited to 'target/linux/generic/backport-5.10/738-v5.14-02-net-dsa-qca8k-check-the-correct-variable-in-qca8k-se.patch')
0 files changed, 0 insertions, 0 deletions