From: Stefan Roesch <[email protected]>
To: <[email protected]>, <[email protected]>
Cc: <[email protected]>, <[email protected]>
Subject: [PATCH v3 0/6] liburing: add support for large CQE sizes
Date: Mon, 25 Apr 2022 11:26:33 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
This adds support for large CQE sizes in the liburing layer. The large CQE
sizes double the size compared to the default CQE size.
To support larger CQE sizes the mmap call needs to be modified to map a larger
memory region for large CQE's. For default CQE's the size of the mapping stays
the same.
Also the ring size calculation needs to change.
Finally when large CQE's are indexed, they need to take into account the bigger
CQE size. The index manipulation remains unchanged, only when the CQE array is
accessed, the offset is changed for large CQE's.
The nop test has been modified to test that the new values are set correctly.
Testing:
The liburing test suite has been run with the four different configurations:
- default
- large SQE
- large CQE
- large SQE & large CQE
To do this the default setting has been changed for the test run to the above
values.:
To use these changes, also the corresponding kernel changes are required.
Changes:
V2: the changed kernel definition of io_uring_cqe_extra has been applied to
the first patch in this patch series.
V3: - change definition of extra io_uring_cqe fields like in linux kernel
- remove io_uring_cqe_extra definition
Stefan Roesch (6):
liburing: Update io_uring.h with large CQE kernel changes
liburing: increase mmap size for large CQE's
liburing: return correct ring size for large CQE's
liburing: index large CQE's correctly
liburing: add large CQE tests to nop test
liburing: Test all configurations with NOP test
src/include/liburing.h | 18 +++++++-
src/include/liburing/io_uring.h | 7 ++++
src/queue.c | 6 ++-
src/setup.c | 13 ++++--
test/nop.c | 74 ++++++++++++++++++++-------------
test/test.h | 35 ++++++++++++++++
6 files changed, 117 insertions(+), 36 deletions(-)
create mode 100644 test/test.h
base-commit: c0ba24d1215e9f2b08266b28b35436988c6f3543
--
2.30.2
next reply other threads:[~2022-04-25 18:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-25 18:26 Stefan Roesch [this message]
2022-04-25 18:26 ` [PATCH v3 1/6] liburing: Update io_uring.h with large CQE kernel changes Stefan Roesch
2022-04-25 18:26 ` [PATCH v3 2/6] liburing: increase mmap size for large CQE's Stefan Roesch
2022-04-25 18:26 ` [PATCH v3 3/6] liburing: return correct ring " Stefan Roesch
2022-04-25 18:26 ` [PATCH v3 4/6] liburing: index large CQE's correctly Stefan Roesch
2022-04-25 18:26 ` [PATCH v3 5/6] liburing: add large CQE tests to nop test Stefan Roesch
2022-04-25 18:26 ` [PATCH v3 6/6] liburing: Test all configurations with NOP test Stefan Roesch
2022-04-25 18:45 ` [PATCH v3 0/6] liburing: add support for large CQE sizes 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] \
[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