From: Jens Axboe <axboe@kernel.dk>
To: io-uring@vger.kernel.org
Subject: [PATCHSET 0/4] Cleanup io_buffer_list and mmap handling
Date: Wed, 3 Apr 2024 07:52:33 -0600 [thread overview]
Message-ID: <20240403135602.1623312-1-axboe@kernel.dk> (raw)
Hi,
This series was previously part of the ring map series targeted for
6.10, where remap_pfn_range() was replaced by vm_insert_pages(). But I
think it can stand on its own and has real fixes in it too and should go
in sooner, so sending it out separately.
Series basically gets rid of the split we have between how lists are
stored depending on their buffer group ID, and stores everything in an
xarray to remove the distinction between the two. With that, we can drop
the io_buffer_list->is_ready as well. Then it adds a separate reference
for the io_buffer_list, and uses that to tighten down how mmap buffer
rings are handled.
The resulting code is simpler and easier to follow, and drops more code
than it adds.
include/linux/io_uring_types.h | 1 -
io_uring/io_uring.c | 13 ++--
io_uring/kbuf.c | 118 ++++++++++++---------------------
io_uring/kbuf.h | 8 ++-
4 files changed, 52 insertions(+), 88 deletions(-)
--
Jens Axboe
next reply other threads:[~2024-04-03 13:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-03 13:52 Jens Axboe [this message]
2024-04-03 13:52 ` [PATCH 1/4] io_uring/kbuf: get rid of lower BGID lists Jens Axboe
2024-04-03 13:52 ` [PATCH 2/4] io_uring/kbuf: get rid of bl->is_ready Jens Axboe
2024-04-03 13:52 ` [PATCH 3/4] io_uring/kbuf: protect io_buffer_list teardown with a reference Jens Axboe
2024-04-03 13:52 ` [PATCH 4/4] io_uring/kbuf: hold io_buffer_list reference over mmap Jens Axboe
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=20240403135602.1623312-1-axboe@kernel.dk \
--to=axboe@kernel.dk \
--cc=io-uring@vger.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).