From: Dylan Yudaken <[email protected]>
To: <[email protected]>
Cc: <[email protected]>, <[email protected]>, <[email protected]>,
Dylan Yudaken <[email protected]>
Subject: [PATCH liburing 0/5] overflow support
Date: Thu, 21 Apr 2022 02:14:22 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
This series adds more support overflow conditions, including testing what happens when an overflow CQE is not able to be allocated.
Patches 1,2,4:
- clean up existing documentation to account for updated kernel behaviour
Patch 3:
- exposes some API to allow applications to inspect overflow state
Patch 5:
- test new overflow API and new kernel error signalling
Dylan Yudaken (5):
fix documentation shortenings
update io_uring_enter.2 docs for IORING_FEAT_NODROP
expose CQ ring overflow state
add docs for overflow lost errors
overflow: add tests
man/io_uring_enter.2 | 24 +++-
man/io_uring_setup.2 | 11 +-
man/io_uring_wait_cqe.3 | 2 +-
man/io_uring_wait_cqe_nr.3 | 2 +-
man/io_uring_wait_cqe_timeout.3 | 2 +-
man/io_uring_wait_cqes.3 | 2 +-
src/include/liburing.h | 10 ++
src/queue.c | 31 +++--
test/cq-overflow.c | 240 +++++++++++++++++++++++++++++++-
9 files changed, 298 insertions(+), 26 deletions(-)
base-commit: b7d8dd8bbf5b8550c8a0c1ed70431cd8050709f0
--
2.30.2
next reply other threads:[~2022-04-21 9:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-21 9:14 Dylan Yudaken [this message]
2022-04-21 9:14 ` [PATCH liburing 1/5] fix documentation shortenings Dylan Yudaken
2022-04-21 9:14 ` [PATCH liburing 2/5] update io_uring_enter.2 docs for IORING_FEAT_NODROP Dylan Yudaken
2022-04-21 9:14 ` [PATCH liburing 3/5] expose CQ ring overflow state Dylan Yudaken
2022-04-21 9:14 ` [PATCH liburing 4/5] add docs for overflow lost errors Dylan Yudaken
2022-04-21 9:14 ` [PATCH liburing 5/5] overflow: add tests Dylan Yudaken
2022-04-21 11:44 ` Ammar Faizi
2022-04-21 13:04 ` Dylan Yudaken
2022-04-21 19:49 ` 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] \
[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