From: Jens Axboe <axboe@kernel.dk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: io-uring <io-uring@vger.kernel.org>
Subject: [GIT PULL] io_uring fixes for 6.15-rc3
Date: Fri, 18 Apr 2025 08:46:02 -0600 [thread overview]
Message-ID: <a88f9dd9-5bcd-4103-8df6-3dd8d29288e9@kernel.dk> (raw)
Hi Linus,
Set of fixes for io_uring that should go into the 6.15 kernel release.
This pull request contains:
- Set of patches correctly capping iov_iter->nr_segs for imports of
registered buffers, both kbuf and normal ones. 3 cleanups to make it
saner first, then two fixes for each of the buffer types. Fixes a
performance regression where partial buffer usage doesn't trim the
tail number of segments, leading the block layer to iterate the IOs to
check if it needs splitting.
- Two patches tweaking the newly introduced zero-copy rx API, mostly to
keep the API consistent once we add multiple interface queues per ring
support in the 6.16 release.
- zc rx unmapping fix for a dead device
Please pull!
The following changes since commit cf960726eb65e8d0bfecbcce6cf95f47b1ffa6cc:
io_uring/kbuf: reject zero sized provided buffers (2025-04-07 07:51:23 -0600)
are available in the Git repository at:
git://git.kernel.dk/linux.git tags/io_uring-6.15-20250418
for you to fetch changes up to f12ecf5e1c5eca48b8652e893afcdb730384a6aa:
io_uring/zcrx: fix late dma unmap for a dead dev (2025-04-18 06:12:10 -0600)
----------------------------------------------------------------
io_uring-6.15-20250418
----------------------------------------------------------------
Jens Axboe (1):
io_uring/rsrc: ensure segments counts are correct on kbuf buffers
Nitesh Shetty (1):
io_uring/rsrc: send exact nr_segs for fixed buffer
Pavel Begunkov (6):
io_uring/zcrx: return ifq id to the user
io_uring/zcrx: add pp to ifq conversion helper
io_uring/rsrc: don't skip offset calculation
io_uring/rsrc: separate kbuf offset adjustments
io_uring/rsrc: refactor io_import_fixed
io_uring/zcrx: fix late dma unmap for a dead dev
include/uapi/linux/io_uring.h | 4 +-
io_uring/rsrc.c | 92 ++++++++++++++++++++++---------------------
io_uring/zcrx.c | 37 ++++++++++++-----
io_uring/zcrx.h | 1 +
4 files changed, 79 insertions(+), 55 deletions(-)
--
Jens Axboe
next reply other threads:[~2025-04-18 14:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-18 14:46 Jens Axboe [this message]
2025-04-18 16:45 ` [GIT PULL] io_uring fixes for 6.15-rc3 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=a88f9dd9-5bcd-4103-8df6-3dd8d29288e9@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