summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python
diff options
context:
space:
mode:
authorOvidiu Panait <ovidiu.panait.rb@renesas.com>2026-07-22 08:53:53 +0000
committerGeert Uytterhoeven <geert+renesas@glider.be>2026-09-02 14:32:37 +0200
commit2ac7bad110be6ebe478d6bd57821f7f5259a1f54 (patch)
treefae41ca5ca22c05801a9107d5e074a016d944b08 /tools/perf/scripts/python
parentf9d9a1913c09366bf7b967d39575e06cb80128dc (diff)
downloadlinux-next-2ac7bad110be6ebe478d6bd57821f7f5259a1f54.tar.gz
linux-next-2ac7bad110be6ebe478d6bd57821f7f5259a1f54.zip
arm64: dts: renesas: r9a09g087: Switch GBETH TX queue scheduling to WRR
The GBETH ethernet nodes don't specify a TX scheduling policy, so stmmac falls back to Strict Priority. In this configuration the queue with the highest priority gets all the traffic, starving the others under load. Under sustained UDP TX load with multiple data streams, this starvation triggers spurious adapter resets due to TX queue timeouts: iperf3 -c <ip> -i0 -t60 --bind-dev end0 -u -b0 -P4 end0: NETDEV WATCHDOG: CPU: 1: transmit queue 1 timed out 5228 ms end0: Reset adapter. Investigation shows that only the highest priority queue is advancing while the others stall for more than 5 seconds, causing a netdev watchdog reset. Switch the TX scheduling policy to Weighted-Round-Robin (WRR) so that traffic is processed across all queues, eliminating the stalls. Fixes: c4698a34993b ("arm64: dts: renesas: r9a09g087: Add GMAC nodes") Signed-off-by: Ovidiu Panait <ovidiu.panait.rb@renesas.com> Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be> Link: https://patch.msgid.link/20260722085353.136986-6-ovidiu.panait.rb@renesas.com Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions