From: Nicolai Buchwitz <nb@tipi-net.de>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Doug Berger <opendmb@gmail.com>,
Florian Fainelli <florian.fainelli@broadcom.com>,
bcm-kernel-feedback-list@broadcom.com,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
Justin Chen <justin.chen@broadcom.com>,
Ovidiu Panait <ovidiu.panait.rb@renesas.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 0/3] net: bcmgenet: collapse TX priority queues
Date: Mon, 15 Jun 2026 13:35:57 +0200 [thread overview]
Message-ID: <59249267ef946bb39b647fb9cc816c98@tipi-net.de> (raw)
In-Reply-To: <20260613145745.36c5403e@kernel.org>
Hi Jakub
On 13.6.2026 23:57, Jakub Kicinski wrote:
> On Fri, 12 Jun 2026 22:59:12 +0200 Nicolai Buchwitz wrote:
>> Tested on Raspberry Pi CM4 (BCM2711):
>> - Ovidiu's reproducer (iperf3 -u -b0 -P16 -t60) no longer trips
>> NETDEV_WATCHDOG.
>> - UDP sustains 956 Mbit/s line rate over 60 s with 0 datagrams
>> lost (0/4952890).
>> - Single-stream TCP throughput unchanged at 943 Mbit/s.
>
> Of course it has no impact on a single TCP stream test, since TCP
> stream can only use one queue. If anything it should help.
> The testing here is not very convincing. At least install a realistic
> qdisc (fq/fq_codel/cake) and run multi-stream test with multiple cores?
> What's the CPU idle delta in such a test?
Fair. Tests I ran with fq_codel:
# TCP
iperf3 -c <remote> -P 16
# UDP
iperf3 -c <remote> -u -b 1000M -P 16
# RR
iperf3 -c <remote> -t 60 &
netperf -H <remote> -t TCP_RR -l 30 -- -r 1,1
With the following results (all based on net-next with PP):
PP PP+WRR PP+series
TCP -P16 Mbit/s 938 941 941
TCP retransmits 56228 57679 48606
UDP -b1000M -P16 Mbit/s 956 956 956
TCP_RR under TCP load 451.7 453.8 596.8
CPU idle 91.55% 90.53% 90.97%
CPU0 softirq 32.6% 33.4% 33.5%
CPU1-3 idle (avg) 97.6% 97.7% 97.7%
So WRR fixes the watchdog issue, otherwise is within noise. This series
adds ~31% TCP_RR under load and reduces retransmits by ~14%. Note, that
bcmgenet on BCM2711 has only two IRQs and no per-queue affinity, so all
HW interrupts are handled by one core regardless of queue count.
>
> The reason for this change is not coming thru from the submission.
> Ovidiu's patch makes much more intuitive sense. I'll apply that,
> please rebase.
Will rebase and resend with a hopefully better reasoning :)
Thanks
Nicolai
prev parent reply other threads:[~2026-06-15 11:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-12 20:59 [PATCH net-next 0/3] net: bcmgenet: collapse TX priority queues Nicolai Buchwitz
2026-06-12 20:59 ` [PATCH net-next 1/3] net: bcmgenet: collapse TX priority queues to a single queue Nicolai Buchwitz
2026-06-15 18:40 ` Justin Chen
2026-06-12 20:59 ` [PATCH net-next 2/3] net: bcmgenet: remove dead priority queue plumbing Nicolai Buchwitz
2026-06-15 18:40 ` Justin Chen
2026-06-12 20:59 ` [PATCH net-next 3/3] net: bcmgenet: allocate a single-queue netdev Nicolai Buchwitz
2026-06-15 18:40 ` Justin Chen
2026-06-13 21:57 ` [PATCH net-next 0/3] net: bcmgenet: collapse TX priority queues Jakub Kicinski
2026-06-15 11:35 ` Nicolai Buchwitz [this message]
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=59249267ef946bb39b647fb9cc816c98@tipi-net.de \
--to=nb@tipi-net.de \
--cc=andrew+netdev@lunn.ch \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=florian.fainelli@broadcom.com \
--cc=justin.chen@broadcom.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=opendmb@gmail.com \
--cc=ovidiu.panait.rb@renesas.com \
--cc=pabeni@redhat.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