From: Bijan Mottahedeh <[email protected]>
To: [email protected], [email protected]
Subject: [PATCH v2 00/10] liburing: buffer registration enhancements
Date: Fri, 22 Jan 2021 14:54:49 -0800 [thread overview]
Message-ID: <[email protected]> (raw)
v2:
- manpage updates
- additional sharing test cases
This patchset is the liburing changes for buffer registration enhancements.
Patch 1-2 implement the actual liburing changes
Patch 3-4 are the buffer-registration/update tests, copied from
corresponding file tests and adapted for buffers
Patch 5-7 are the buffer-sharing tests.
Patch 8-10 are the man page changes.
Bijan Mottahedeh (10):
liburing: support buffer registration updates
liburing: support buffer registration sharing
test/buffer-register: add buffer registration test
test/buffer-update: add buffer registration update test
test/buffer-share: add buffer registration sharing test
test/buffer-share: add private memory option
test/buffer-share: add interruptible deadlock test
man/io_uring_setup.2: document buffer registration sharing
man/io_uring_register.2: document buffer registration updates
man/io_uring_enter.2: document IORING_OP_BUFFERS_UPDATE
.gitignore | 3 +
man/io_uring_enter.2 | 16 +
man/io_uring_register.2 | 29 +-
man/io_uring_setup.2 | 12 +
src/include/liburing.h | 12 +
src/include/liburing/io_uring.h | 11 +
src/register.c | 29 +-
test/Makefile | 7 +
test/buffer-register.c | 701 +++++++++++++++++++++
test/buffer-share.c | 1282 +++++++++++++++++++++++++++++++++++++++
test/buffer-update.c | 165 +++++
11 files changed, 2260 insertions(+), 7 deletions(-)
create mode 100644 test/buffer-register.c
create mode 100644 test/buffer-share.c
create mode 100644 test/buffer-update.c
--
1.8.3.1
next reply other threads:[~2021-01-22 22:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-22 22:54 Bijan Mottahedeh [this message]
2021-01-22 22:54 ` [PATCH v2 01/10] liburing: support buffer registration updates Bijan Mottahedeh
2021-01-22 22:54 ` [PATCH v2 02/10] liburing: support buffer registration sharing Bijan Mottahedeh
2021-01-22 22:54 ` [PATCH v2 03/10] test/buffer-register: add buffer registration test Bijan Mottahedeh
2021-01-22 22:54 ` [PATCH v2 04/10] test/buffer-update: add buffer registration update test Bijan Mottahedeh
2021-01-22 22:54 ` [PATCH v2 05/10] test/buffer-share: add buffer registration sharing test Bijan Mottahedeh
2021-01-22 22:54 ` [PATCH v2 06/10] test/buffer-share: add private memory option Bijan Mottahedeh
2021-01-22 22:54 ` [PATCH v2 07/10] test/buffer-share: add interruptible deadlock test Bijan Mottahedeh
2021-01-22 22:54 ` [PATCH v2 08/10] man/io_uring_setup.2: document buffer registration sharing Bijan Mottahedeh
2021-01-22 22:54 ` [PATCH v2 09/10] man/io_uring_register.2: document buffer registration updates Bijan Mottahedeh
2021-01-22 22:54 ` [PATCH v2 10/10] man/io_uring_enter.2: document IORING_OP_BUFFERS_UPDATE 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=1611356099-60732-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