From: sashiko-bot@kernel.org
To: "Ovidiu Panait" <ovidiu.panait.rb@renesas.com>
Cc: wsa+renesas@sang-engineering.com, conor+dt@kernel.org,
robh@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 2/5] arm64: dts: renesas: r9a09g056: Switch GBETH TX queue scheduling to WRR
Date: Wed, 22 Jul 2026 09:04:10 +0000 [thread overview]
Message-ID: <20260722090410.CC1D31F00A3A@smtp.kernel.org> (raw)
In-Reply-To: <20260722085353.136986-3-ovidiu.panait.rb@renesas.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
Pre-existing issues:
- [High] This problem wasn't introduced by this patch, but the exact same missing `snps,tx-sched-wrr` bug remains unfixed in sibling SoCs (r9a09g047.dtsi, r9a09g077.dtsi, and r9a09g087.dtsi) that share the same GBETH hardware configuration (`renesas,rzv2h-gbeth` + `snps,dwmac-5.20`). Without specifying the WRR scheduling policy and weights, they will continue to experience Strict Priority queue starvation and netdev watchdog resets under heavy TX load.
--
--- Patch [2]: [PATCH 2/5] arm64: dts: renesas: r9a09g056: Switch GBETH TX queue scheduling to WRR ---
commit 2b31533db8d80852a1d20d1d3d37f647e9c19c9d
Author: Ovidiu Panait <ovidiu.panait.rb@renesas.com>
arm64: dts: renesas: r9a09g056: 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. This starvation triggers spurious adapter resets due
to TX queue timeouts. Switch the TX scheduling policy to Weighted-Round-Robin
(WRR) so that traffic is processed across all queues, eliminating the stalls.
> diff --git a/arch/arm64/boot/dts/renesas/r9a09g056.dtsi b/arch/arm64/boot/dts/renesas/r9a09g056.dtsi
> index d6c8c39df2a4d..281500d9ee42a 100644
> --- a/arch/arm64/boot/dts/renesas/r9a09g056.dtsi
> +++ b/arch/arm64/boot/dts/renesas/r9a09g056.dtsi
> @@ -1569,23 +1569,28 @@ queue3 {
>
> mtl_tx_setup0: tx-queues-config {
> snps,tx-queues-to-use = <4>;
> + snps,tx-sched-wrr;
[Severity: High]
This is a pre-existing issue, but the exact same missing snps,tx-sched-wrr
configuration remains unfixed in sibling SoCs that share the same GBETH
hardware configuration.
Without specifying the WRR scheduling policy and weights, will these other
SoCs continue to experience Strict Priority queue starvation and netdev
watchdog resets under heavy TX load?
For example, in arch/arm64/boot/dts/renesas/r9a09g047.dtsi:mtl_tx_setup0:
mtl_tx_setup0: tx-queues-config {
snps,tx-queues-to-use = <4>;
queue0 {
snps,dcb-algorithm;
snps,priority = <0x1>;
};
The same applies to r9a09g077.dtsi and r9a09g087.dtsi.
Should a similar update be applied to these sibling SoCs?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260722085353.136986-1-ovidiu.panait.rb@renesas.com?part=2
next prev parent reply other threads:[~2026-07-22 9:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-22 8:53 [PATCH 0/5] Fix GBETH TX scheduling policy for RZ/{V2H, V2N, G3E, T2H, N2H} Ovidiu Panait
2026-07-22 8:53 ` [PATCH 1/5] arm64: dts: renesas: r9a09g057: Switch GBETH TX queue scheduling to WRR Ovidiu Panait
2026-07-22 8:53 ` [PATCH 2/5] arm64: dts: renesas: r9a09g056: " Ovidiu Panait
2026-07-22 9:04 ` sashiko-bot [this message]
2026-07-22 8:53 ` [PATCH 3/5] arm64: dts: renesas: r9a09g047: " Ovidiu Panait
2026-07-22 8:53 ` [PATCH 4/5] arm64: dts: renesas: r9a09g077: " Ovidiu Panait
2026-07-22 9:07 ` sashiko-bot
2026-07-22 8:53 ` [PATCH 5/5] arm64: dts: renesas: r9a09g078: " Ovidiu Panait
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260722090410.CC1D31F00A3A@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=ovidiu.panait.rb@renesas.com \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=wsa+renesas@sang-engineering.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox