From: patchwork-bot+netdevbpf@kernel.org
To: Avi Weiss <thnkslprpt@gmail.com>
Cc: akiyano@amazon.com, darinzon@amazon.com, netdev@vger.kernel.org,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@kernel.org,
kuba@kernel.org, pabeni@redhat.com
Subject: Re: [PATCH net] net: ena: avoid RX copybreak for multi-descriptor packets
Date: Wed, 11 Nov 2026 23:10:05 +0000 [thread overview]
Message-ID: <179443860518.1696522.1305639558376761681.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261109141343.920187-2-thnkslprpt@gmail.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 9 Nov 2026 16:13:44 +0200 you wrote:
> ena_rx_skb() selects the copybreak path based on the first RX
> descriptor's length without checking the number of descriptors. When
> a packet spans multiple descriptors, this copies only the first
> buffer into the skb and fails to recycle the remaining request IDs,
> while RX cleanup advances by the full descriptor count.
>
> Restrict copybreak to single-descriptor packets and apply the same
> restriction to the rx_copybreak_pkt statistic. Multi-descriptor
> packets then use the existing fragment-processing path.
>
> [...]
Here is the summary with links:
- [net] net: ena: avoid RX copybreak for multi-descriptor packets
https://git.kernel.org/netdev/net/c/f3c790c34d22
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 23:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-09 14:13 [PATCH net] net: ena: avoid RX copybreak for multi-descriptor packets Avi Weiss
2026-11-11 23: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=179443860518.1696522.1305639558376761681.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=akiyano@amazon.com \
--cc=andrew+netdev@lunn.ch \
--cc=darinzon@amazon.com \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=thnkslprpt@gmail.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