From: Pavel Begunkov <[email protected]>
To: Jens Axboe <[email protected]>, [email protected]
Subject: [RFC v2 00/12] dynamic buffers + rsrc tagging
Date: Sun, 25 Apr 2021 14:32:14 +0100 [thread overview]
Message-ID: <[email protected]> (raw)
1) support dynamic managment for registered buffers, including
update.
2) add new IORING_REGISTER* for rsrc register and rsrc update,
which are just dispatch files/buffers to right callbacks. Needed
because old ones not nicely extendible. The downside --
restrictions not supporting it with fine granularity.
3) add rsrc tagging, with tag=0 ingnoring CQE posting.
Doesn't post CQEs on unregister, but can easily be changed
v2: instead of async_data importing for fixed rw, save
used io_mapped_ubuf and use it on re-import.
Add patch 9/12 as a preparation for that.
Fix prep rw getting a rsrc node ref for fixed files without
having a rsrc node.
Bijan Mottahedeh (1):
io_uring: implement fixed buffers registration similar to fixed files
Pavel Begunkov (11):
io_uring: move __io_sqe_files_unregister
io_uring: return back rsrc data free helper
io_uring: decouple CQE filling from requests
io_uring: preparation for rsrc tagging
io_uring: add generic path for rsrc update
io_uring: enumerate dynamic resources
io_uring: add IORING_REGISTER_RSRC
io_uring: add generic rsrc update with tags
io_uring: keep table of pointers to ubufs
io_uring: prepare fixed rw for dynanic buffers
io_uring: add full-fledged dynamic buffers support
fs/io_uring.c | 523 +++++++++++++++++++++++++---------
include/uapi/linux/io_uring.h | 23 ++
2 files changed, 405 insertions(+), 141 deletions(-)
--
2.31.1
next reply other threads:[~2021-04-25 13:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-25 13:32 Pavel Begunkov [this message]
2021-04-25 13:32 ` [PATCH v2 01/12] io_uring: move __io_sqe_files_unregister Pavel Begunkov
2021-04-25 13:32 ` [PATCH v2 02/12] io_uring: return back rsrc data free helper Pavel Begunkov
2021-04-25 13:32 ` [PATCH v2 03/12] io_uring: decouple CQE filling from requests Pavel Begunkov
2021-04-25 13:32 ` [PATCH v2 04/12] io_uring: preparation for rsrc tagging Pavel Begunkov
2021-04-25 13:32 ` [PATCH v2 05/12] io_uring: add generic path for rsrc update Pavel Begunkov
2021-04-25 13:32 ` [PATCH v2 06/12] io_uring: enumerate dynamic resources Pavel Begunkov
2021-04-25 13:32 ` [PATCH v2 07/12] io_uring: add IORING_REGISTER_RSRC Pavel Begunkov
2021-04-25 13:32 ` [PATCH v2 08/12] io_uring: add generic rsrc update with tags Pavel Begunkov
2021-04-25 13:32 ` [PATCH v2 09/12] io_uring: keep table of pointers to ubufs Pavel Begunkov
2021-04-25 13:32 ` [PATCH v2 10/12] io_uring: prepare fixed rw for dynanic buffers Pavel Begunkov
2021-04-25 13:32 ` [PATCH v2 11/12] io_uring: implement fixed buffers registration similar to fixed files Pavel Begunkov
2021-04-25 13:32 ` [PATCH v2 12/12] io_uring: add full-fledged dynamic buffers support Pavel Begunkov
2021-04-25 16:15 ` [RFC v2 00/12] dynamic buffers + rsrc tagging 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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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