From: Jens Axboe <axboe@kernel.dk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: io-uring <io-uring@vger.kernel.org>
Subject: [GIT PULL] Large buffer support for zcrx
Date: Thu, 12 Feb 2026 04:22:38 -0700 [thread overview]
Message-ID: <7eff267c-a76a-43e1-87a5-d92148abdc7d@kernel.dk> (raw)
Hi Linus,
Now that the net PR is upstream, here's support for large buffers for
zcrx. Using larger (bigger than 4K) rx buffers can increase the effiency
of zcrx. For example, it's been shown that using 32K buffers can
decrease CPU usage by ~30% compared to 4K buffers. Please pull!
The following changes since commit d1de61db1536727c1cad049c09decff22e8b6dd7:
io_uring/zcrx: document area chunking parameter (2026-01-14 02:13:37 +0000)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux.git tags/for-7.0/io_uring-zcrx-large-buffers-20260206
for you to fetch changes up to 795663b4d160ba652959f1a46381c5e8b1342a53:
io_uring/zcrx: implement large rx buffer support (2026-01-24 08:33:03 -0700)
----------------------------------------------------------------
for-7.0/io_uring-zcrx-large-buffers-20260206
----------------------------------------------------------------
Pavel Begunkov (1):
io_uring/zcrx: implement large rx buffer support
include/uapi/linux/io_uring.h | 2 +-
io_uring/zcrx.c | 38 +++++++++++++++++++++++++++++++++-----
2 files changed, 34 insertions(+), 6 deletions(-)
--
Jens Axboe
next reply other threads:[~2026-02-12 11:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-12 11:22 Jens Axboe [this message]
2026-02-13 1:18 ` [GIT PULL] Large buffer support for zcrx pr-tracker-bot
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=7eff267c-a76a-43e1-87a5-d92148abdc7d@kernel.dk \
--to=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=torvalds@linux-foundation.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