From: patchwork-bot+netdevbpf@kernel.org
To: Kordian Chmielewski <kudzo51@gmail.com>
Cc: netdev@vger.kernel.org, f.fainelli@gmail.com,
florian.fainelli@broadcom.com, rafal@milecki.pl,
bcm-kernel-feedback-list@broadcom.com, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@kernel.org, kuba@kernel.org,
pabeni@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v3 0/7] net: bcm4908_enet: TX ring and DMA fixes
Date: Fri, 20 Nov 2026 02:00:06 +0000 [thread overview]
Message-ID: <179514000678.3977048.3079257794014702506.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261113235847.517308-1-kudzo51@gmail.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sat, 14 Nov 2026 00:58:40 +0100 you wrote:
> These fix the BCM4908 Ethernet driver. Patch 1 fixes a TX stall seen
> on a TP-Link Archer AX6000 under sustained load. Patches 2 to 7 come
> from reading the code and from review, and have no reproducer.
>
> Tested on an Archer AX6000 with OpenWrt and Linux 6.18.55, whose driver
> differs from net only in one tree-wide change, with the LAN going
> through this driver: TX and RX at line rate (941 Mbit/s TCP), and four
> ifdown/ifup cycles of the conduit while it was sending. I ran the same
> again, plus a UDP stream at 1 Gbit/s (944 Mbit/s received), with the TX
> ring shrunk to 16 descriptors for the test, so that the queue was
> stopped and woken over and over (about a million qdisc requeues in a
> minute, with the ring full or nearly full in a third of the one-second
> samples). No stall, no errors in the counters, no DMA timeout warnings.
>
> [...]
Here is the summary with links:
- [net,v3,1/7] net: bcm4908_enet: fix the TX ring wrap
https://git.kernel.org/netdev/net/c/4f8b1a7cf754
- [net,v3,2/7] net: bcm4908_enet: drop a TX frame whose DMA mapping failed
https://git.kernel.org/netdev/net/c/e1d4683fb4cb
- [net,v3,3/7] net: bcm4908_enet: release the TX ring on stop
https://git.kernel.org/netdev/net/c/e2785f0ff0a2
- [net,v3,4/7] net: bcm4908_enet: unmap the buffer of a dropped RX frame
https://git.kernel.org/netdev/net/c/1b48d619448c
- [net,v3,5/7] net: bcm4908_enet: unmap RX buffers on stop with their mapped size
https://git.kernel.org/netdev/net/c/1da02595e8d2
- [net,v3,6/7] net: bcm4908_enet: publish the buffer address before OWN
https://git.kernel.org/netdev/net/c/4d47e6c2f3ce
- [net,v3,7/7] net: bcm4908_enet: order the TX ring index accesses
https://git.kernel.org/netdev/net/c/ebe31472ad0a
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-11-20 2:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-13 23:58 [PATCH net v3 0/7] net: bcm4908_enet: TX ring and DMA fixes Kordian Chmielewski
2026-11-13 23:58 ` [PATCH net v3 1/7] net: bcm4908_enet: fix the TX ring wrap Kordian Chmielewski
2026-11-14 23:59 ` netdev-bot+sashiko
2026-11-15 13:49 ` Kordian Chmielewski
2026-11-13 23:58 ` [PATCH net v3 2/7] net: bcm4908_enet: drop a TX frame whose DMA mapping failed Kordian Chmielewski
2026-11-13 23:58 ` [PATCH net v3 3/7] net: bcm4908_enet: release the TX ring on stop Kordian Chmielewski
2026-11-14 23:59 ` netdev-bot+sashiko
2026-11-15 13:49 ` Kordian Chmielewski
2026-11-13 23:58 ` [PATCH net v3 4/7] net: bcm4908_enet: unmap the buffer of a dropped RX frame Kordian Chmielewski
2026-11-13 23:58 ` [PATCH net v3 5/7] net: bcm4908_enet: unmap RX buffers on stop with their mapped size Kordian Chmielewski
2026-11-13 23:58 ` [PATCH net v3 6/7] net: bcm4908_enet: publish the buffer address before OWN Kordian Chmielewski
2026-11-13 23:58 ` [PATCH net v3 7/7] net: bcm4908_enet: order the TX ring index accesses Kordian Chmielewski
2026-11-20 2:00 ` patchwork-bot+netdevbpf [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=179514000678.3977048.3079257794014702506.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=florian.fainelli@broadcom.com \
--cc=kuba@kernel.org \
--cc=kudzo51@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rafal@milecki.pl \
/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