From: Bijan Mottahedeh <[email protected]>
To: [email protected], [email protected]
Subject: [RFC 0/8] io_uring: buffer registration enhancements
Date: Thu, 22 Oct 2020 16:13:55 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
Hi Jens,
This RFC implements a set of enhancements to buffer registration consistent
with existing file registration functionality:
- buffer registration updates IORING_REGISTER_BUFFERS_UPDATE
IORING_OP_BUFFERS_UPDATE
- readv/writev with fixed buffers IOSQE_FIXED_BUFFER
- buffer registration sharing IORING_SETUP_SHARE_BUF
IORING_SETUP_ATTACH_BUF
Patches 1,2 modularize existing buffer registration code.
Patch 3 generalizes fixed_file functionality to fixed_rsrc.
Patch 4 applies fixed_rsrc functionality for fixed buffers support.
Patch 5 generalizes files_update functionality to rsrc_update.
Patch 6 implements buffer registration update, and introduces
IORING_REGISTER_BUFFERS_UPDATE and IORING_OP_BUFFERS_UPDATE, consistent
with file registration update.
Patch 7 implements readv/writev support with fixed buffers, and introduces
IOSQE_FIXED_BUFFER, consistent with fixed files.
Patch 8 implements buffer sharing among multiple rings; it works as
follows based on previous conversations:
- A new ring, A, is setup. Since no buffers have been registered, the
registered buffer state is an empty set, Z. That's different from the
NULL state in current implementation.
- Ring B is setup, attaching to Ring A. It's also attaching to it's
buffer registrations, now we have two references to the same empty
set, Z.
- Ring A registers buffers into set Z, which is no longer empty.
- Ring B sees this immediately, since it's already sharing that set.
TBD
- I think I have to add IORING_UNREGISTER_BUFFERS to
io_register_op_must_quiesce() but wanted to confirm.
- IORING_OP_SHUTDOWN has been removed but still in liburing, not sure why.
I wanted to verify before removing that functionality.
I have used liburing file-{register,update} tests as models for
buffer-{register,update}, and it seems to work ok.
Bijan Mottahedeh (8):
io_uring: modularize io_sqe_buffer_register
io_uring: modularize io_sqe_buffers_register
io_uring: generalize fixed file functionality
io_uring: implement fixed buffers registration similar to fixed files
io_uring: generalize files_update functionlity to rsrc_update
io_uring: support buffer registration updates
io_uring: support readv/writev with fixed buffers
io_uring: support buffer registration sharing
fs/io_uring.c | 1021 ++++++++++++++++++++++++++++++++---------
include/uapi/linux/io_uring.h | 15 +-
2 files changed, 807 insertions(+), 229 deletions(-)
--
1.8.3.1
next reply other threads:[~2020-10-22 23:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-22 23:13 Bijan Mottahedeh [this message]
2020-10-22 23:13 ` [RFC 1/8] io_uring: modularize io_sqe_buffer_register Bijan Mottahedeh
2020-10-22 23:13 ` [RFC 2/8] io_uring: modularize io_sqe_buffers_register Bijan Mottahedeh
2020-10-22 23:13 ` [RFC 3/8] io_uring: generalize fixed file functionality Bijan Mottahedeh
2020-10-22 23:13 ` [RFC 4/8] io_uring: implement fixed buffers registration similar to fixed files Bijan Mottahedeh
2020-10-22 23:14 ` [RFC 5/8] io_uring: generalize files_update functionlity to rsrc_update Bijan Mottahedeh
2020-10-22 23:14 ` [RFC 6/8] io_uring: support buffer registration updates Bijan Mottahedeh
2020-10-22 23:14 ` [RFC 7/8] io_uring: support readv/writev with fixed buffers Bijan Mottahedeh
2020-10-22 23:14 ` [RFC 8/8] io_uring: support buffer registration sharing Bijan Mottahedeh
2020-10-30 17:11 ` [RFC 0/8] io_uring: buffer registration enhancements Bijan Mottahedeh
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=1603408443-51303-1-git-send-email-bijan.mottahedeh@oracle.com \
[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