summaryrefslogtreecommitdiff
path: root/scripts/Makefile.thinlto
diff options
context:
space:
mode:
authorRosen Penev <rosenp@gmail.com>2026-10-18 16:16:29 -0700
committerJakub Kicinski <kuba@kernel.org>2026-10-21 17:29:58 -0700
commit77dac783f113dcc4576efca6f4391d7324c0b1fc (patch)
treed85af4e410a4824b16dcad80619b17a1f4a4f23a /scripts/Makefile.thinlto
parent5a3dcad8e101ddcd3a886907c8992df54472f749 (diff)
downloadlinux-77dac783f113dcc4576efca6f4391d7324c0b1fc.tar.gz
linux-77dac783f113dcc4576efca6f4391d7324c0b1fc.zip
net: bgmac: rate limit RX error messages
When the RX ring is full the RX FIFO overflows. With RX overflow continue enabled, the DMA engine then writes one frame with a bogus length (always 0x45c2 on a BCM4716), which the driver drops with "Found oversized packet at slot %d, DMA issue!". Under sustained overload this happens on every NAPI poll. On an Asus RT-N16 a 950 Mbit/s UDP stream to the router printed about 1450 such lines in 20 seconds. The messages are printed from NAPI context, so with a serial console the router spends most of its time printing. The frames are already accounted in rx_length_errors and rx_errors. Rate limit both RX error messages. With this change the same flood printed 60 lines while rx_length_errors counted 14297 dropped frames. Signed-off-by: Rosen Penev <rosenp@gmail.com> Reviewed-by: Daniel Machon <daniel.machon@microchip.com> Link: https://patch.msgid.link/20261018231629.39734-1-rosenp@gmail.com Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'scripts/Makefile.thinlto')
0 files changed, 0 insertions, 0 deletions