From: patchwork-bot+netdevbpf@kernel.org
To: Dimitri Daskalakis <dimitri.daskalakis1@gmail.com>
Cc: davem@davemloft.net, alexanderduyck@fb.com, kuba@kernel.org,
edumazet@google.com, pabeni@redhat.com, andrew+netdev@lunn.ch,
horms@kernel.org, mike.marciniszyn@gmail.com, lee@trager.us,
jacob.e.keller@intel.com, mohsin.bashr@gmail.com,
almasrymina@google.com, netdev@vger.kernel.org,
kernel-team@meta.com
Subject: Re: [PATCH net 0/2] Fix page fragment handling when PAGE_SIZE > 4K
Date: Sat, 28 Mar 2026 03:40:14 +0000 [thread overview]
Message-ID: <177466921428.4169512.12440330427205497180.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260324195123.3486219-1-dimitri.daskalakis1@gmail.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 24 Mar 2026 12:51:21 -0700 you wrote:
> From: Dimitri Daskalakis <daskald@meta.com>
>
> FBNIC operates on fixed size descriptors (4K). When the OS supports pages
> larger than 4K, we fragment the page across multiple descriptors.
>
> While performance testing, I found several issues with our page fragment
> handling, resulting in low throughput and potential RX stalls.
>
> [...]
Here is the summary with links:
- [net,1/2] eth: fbnic: Account for page fragments when updating BDQ tail
https://git.kernel.org/netdev/net/c/b38c55320bf8
- [net,2/2] eth: fbnic: Fix debugfs output for BDQ's with page frags
https://git.kernel.org/netdev/net/c/f3567dd428b2
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-03-28 3:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-24 19:51 [PATCH net 0/2] Fix page fragment handling when PAGE_SIZE > 4K Dimitri Daskalakis
2026-03-24 19:51 ` [PATCH net 1/2] eth: fbnic: Account for page fragments when updating BDQ tail Dimitri Daskalakis
2026-03-24 19:51 ` [PATCH net 2/2] eth: fbnic: Fix debugfs output for BDQ's with page frags Dimitri Daskalakis
2026-03-28 3:29 ` [PATCH net 0/2] Fix page fragment handling when PAGE_SIZE > 4K Jakub Kicinski
2026-03-28 3:40 ` 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=177466921428.4169512.12440330427205497180.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexanderduyck@fb.com \
--cc=almasrymina@google.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=dimitri.daskalakis1@gmail.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jacob.e.keller@intel.com \
--cc=kernel-team@meta.com \
--cc=kuba@kernel.org \
--cc=lee@trager.us \
--cc=mike.marciniszyn@gmail.com \
--cc=mohsin.bashr@gmail.com \
--cc=netdev@vger.kernel.org \
--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