From: Jens Axboe <[email protected]>
To: [email protected]
Cc: [email protected]
Subject: [PATCHSET v6 0/3] Add support for ring mapped provided buffers
Date: Mon, 16 May 2022 10:21:15 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
Hi,
This series builds to adding support for a different way of doing
provided buffers, which is a lot more efficient than the existing scheme
for high rate of consumption/provision of buffers. The interesting bits
here are patch 3, which also has some performance numbers an an
explanation of it.
Patch 1 adds NOP support for provided buffers, just so that we can
benchmark the last change.
Patch 2 just abstracts out the pinning code.
Patch 3 adds the actual feature.
This passes the full liburing suite, and various test cases I adopted
to use ring provided buffers.
v6:
- Change layout so that 'head' overlaps with reserved field in first
buffer, avoiding the weird split of first page having N-1 buffers and
the rest N (Dylan)
- Rebase on current kernel bits
- Fix missing ring unlock on out-of-bufs
- Fix issue in io_recv()
Can also be found in my git repo, for-5.19/io_uring-pbuf branch:
https://git.kernel.dk/cgit/linux-block/log/?h=for-5.19/io_uring-pbuf
and there's an associated liburing branch too:
https://git.kernel.dk/cgit/liburing/log/?h=huge
fs/io_uring.c | 323 +++++++++++++++++++++++++++++-----
include/uapi/linux/io_uring.h | 36 ++++
2 files changed, 319 insertions(+), 40 deletions(-)
--
Jens Axboe
next reply other threads:[~2022-05-16 16:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-16 16:21 Jens Axboe [this message]
2022-05-16 16:21 ` [PATCH 1/3] io_uring: add buffer selection support to IORING_OP_NOP Jens Axboe
2022-05-16 16:21 ` [PATCH 2/3] io_uring: add io_pin_pages() helper Jens Axboe
2022-05-16 16:21 ` [PATCH 3/3] io_uring: add support for ring mapped supplied buffers Jens Axboe
2022-05-17 14:18 ` Hao Xu
2022-05-17 15:46 ` Jens Axboe
2022-05-18 10:50 ` Hao Xu
2022-05-18 12:48 ` Jens Axboe
2022-05-17 14:20 ` [PATCHSET v6 0/3] Add support for ring mapped provided buffers Hao Xu
2022-05-17 15:44 ` 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