From: patchwork-bot+netdevbpf@kernel.org
To: =?utf-8?b?QmrDtnJuIFTDtnBlbCA8Ympvcm5Aa2VybmVsLm9yZz4=?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org
Cc: alexanderduyck@fb.com, kuba@kernel.org, kernel-team@meta.com,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
pabeni@redhat.com, horms@kernel.org, shuah@kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org, daniel@iogearbox.net,
mike.marciniszyn@gmail.com, mohsin.bashr@gmail.com,
sdf@fomichev.me, bobbyeshleman@meta.com, daskald@meta.com,
bestswngs@gmail.com, maxime.chevallier@bootlin.com,
jacob.e.keller@intel.com, leitao@debian.org, cuitao@kylinos.cn,
asml.silence@gmail.com, dw@davidwei.uk
Subject: Re: [PATCH net-next v4 0/5] fbnic: Support larger RX pages
Date: Thu, 01 Oct 2026 00:30:20 +0000 [thread overview]
Message-ID: <179081462052.2189941.6876682885439352016.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260925104417.2325213-1-bjorn@kernel.org>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 25 Sep 2026 12:44:07 +0200 you wrote:
> Hi!
>
> This series adds support for large io_uring zero-copy RX buffers to
> fbnic.
>
> fbnic hardware consumes receive memory in 4 KiB device pages, while
> io_uring may expose a larger software buffer, such as 256 KiB. Track
> the device-page geometry per BDQ, represent each large buffer with
> consecutive descriptors, and decode completions to the corresponding
> offset within the buffer. HPQ keeps its existing PAGE_SIZE geometry.
>
> [...]
Here is the summary with links:
- [net-next,v4,1/5] net: Add netdev_config helpers
https://git.kernel.org/netdev/net-next/c/c978ff0f1e85
- [net-next,v4,2/5] fbnic: Track BDQ device-page geometry per ring
https://git.kernel.org/netdev/net-next/c/0d5c23f827d3
- [net-next,v4,3/5] net: Revalidate queue config for ringparam changes
https://git.kernel.org/netdev/net-next/c/f092b749e11c
- [net-next,v4,4/5] fbnic: Support larger memory-provider RX pages
https://git.kernel.org/netdev/net-next/c/54491a1dbd68
- [net-next,v4,5/5] selftests: drv-net: Request larger zcrx buffers
https://git.kernel.org/netdev/net-next/c/b7fb14dff027
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-10-01 0:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-25 10:44 Björn Töpel
2026-09-25 10:44 ` [PATCH net-next v4 1/5] net: Add netdev_config helpers Björn Töpel
2026-09-30 16:44 ` Joe Damato
2026-09-25 10:44 ` [PATCH net-next v4 2/5] fbnic: Track BDQ device-page geometry per ring Björn Töpel
2026-09-30 17:08 ` Joe Damato
2026-09-25 10:44 ` [PATCH net-next v4 3/5] net: Revalidate queue config for ringparam changes Björn Töpel
2026-09-30 17:22 ` Joe Damato
2026-09-25 10:44 ` [PATCH net-next v4 4/5] fbnic: Support larger memory-provider RX pages Björn Töpel
2026-09-25 10:44 ` [PATCH net-next v4 5/5] selftests: drv-net: Request larger zcrx buffers Björn Töpel
2026-09-30 11:36 ` [PATCH net-next v4 0/5] fbnic: Support larger RX pages Simon Horman
2026-10-01 0:30 ` 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=179081462052.2189941.6876682885439352016.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc==?utf-8?b?QmrDtnJuIFTDtnBlbCA8Ympvcm5Aa2VybmVsLm9yZz4=?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org \
--cc=alexanderduyck@fb.com \
--cc=andrew+netdev@lunn.ch \
--cc=asml.silence@gmail.com \
--cc=bestswngs@gmail.com \
--cc=bobbyeshleman@meta.com \
--cc=cuitao@kylinos.cn \
--cc=daniel@iogearbox.net \
--cc=daskald@meta.com \
--cc=davem@davemloft.net \
--cc=dw@davidwei.uk \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jacob.e.keller@intel.com \
--cc=kernel-team@meta.com \
--cc=kuba@kernel.org \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=maxime.chevallier@bootlin.com \
--cc=mike.marciniszyn@gmail.com \
--cc=mohsin.bashr@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@fomichev.me \
--cc=shuah@kernel.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®