From: patchwork-bot+netdevbpf@kernel.org
To: Nicolai Buchwitz <nb@tipi-net.de>
Cc: opendmb@gmail.com, florian.fainelli@broadcom.com,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@kernel.org,
kuba@kernel.org, pabeni@redhat.com, justin.chen@broadcom.com,
bcm-kernel-feedback-list@broadcom.com, razor@blackwall.org,
kerneljasonxing@gmail.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v2 0/2] net: bcmgenet: fix tx stalls on 32 descriptor rings
Date: Wed, 11 Nov 2026 01:10:09 +0000 [thread overview]
Message-ID: <179435940916.149955.1533526014657695981.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261109-nb-genet-txq-thld-net-v2-0-efd8f4be96f2@tipi-net.de>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 09 Nov 2026 22:53:00 +0100 you wrote:
> Found this while fixing the clashiko findings on v6 of my MTU series. After
> those fixes this bug would be easier to hit. At the moment it needs a larger
> CONFIG_MAX_SKB_FRAGS than the default.
>
> Queues 1 to 4 hold 32 descriptors, which is less than the Tx path assumes
> in two places with CONFIG_MAX_SKB_FRAGS >= 31.
>
> [...]
Here is the summary with links:
- [net,v2,1/2] net: bcmgenet: cap the Tx queue threshold at the ring size
https://git.kernel.org/netdev/net-next/c/1e09af397bc7
- [net,v2,2/2] net: bcmgenet: flatten frames that cannot fit the ring
https://git.kernel.org/netdev/net-next/c/fbfd7cfd2019
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-11 1:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-09 21:53 Nicolai Buchwitz
2026-11-09 21:53 ` [PATCH net v2 1/2] net: bcmgenet: cap the Tx queue threshold at the ring size Nicolai Buchwitz
2026-11-09 21:53 ` [PATCH net v2 2/2] net: bcmgenet: flatten frames that cannot fit the ring Nicolai Buchwitz
2026-11-09 22:14 ` Florian Fainelli
2026-11-11 1:10 ` 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=179435940916.149955.1533526014657695981.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=florian.fainelli@broadcom.com \
--cc=justin.chen@broadcom.com \
--cc=kerneljasonxing@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nb@tipi-net.de \
--cc=netdev@vger.kernel.org \
--cc=opendmb@gmail.com \
--cc=pabeni@redhat.com \
--cc=razor@blackwall.org \
/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
all inboxes | Powered by JetHome®