From: Pavel Begunkov <[email protected]>
To: [email protected]
Cc: Jens Axboe <[email protected]>, [email protected]
Subject: [PATCH liburing 0/4] Tests for absolute timeouts and clockids
Date: Sun, 18 Aug 2024 19:55:40 +0100 [thread overview]
Message-ID: <[email protected]> (raw)
Add definitions, tests and documentation for IORING_ENTER_ABS_TIMER
and IORING_REGISTER_CLOCK.
It also adds helpers for registering clocks but not for absolute
timeouts. Currently, liburing does't provide a way to pass custom
enter flags.
Pavel Begunkov (4):
Sync kernel headers
src/register: add clock id registration helper
test: test clockids and abs timeouts
man: document clock id and IORING_ENTER_ABS_TIMER
man/io_uring_enter.2 | 12 ++
man/io_uring_register.2 | 20 +++
src/include/liburing.h | 3 +
src/include/liburing/io_uring.h | 67 +++++---
src/liburing-ffi.map | 2 +
src/liburing.map | 2 +
src/register.c | 6 +
test/Makefile | 1 +
test/wait-timeout.c | 283 ++++++++++++++++++++++++++++++++
9 files changed, 369 insertions(+), 27 deletions(-)
create mode 100644 test/wait-timeout.c
--
2.45.2
next reply other threads:[~2024-08-18 18:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-18 18:55 Pavel Begunkov [this message]
2024-08-18 18:55 ` [PATCH liburing 1/4] Sync kernel headers Pavel Begunkov
2024-08-18 18:55 ` [PATCH liburing 2/4] src/register: add clock id registration helper Pavel Begunkov
2024-08-18 18:55 ` [PATCH liburing 3/4] test: test clockids and abs timeouts Pavel Begunkov
2024-08-18 18:55 ` [PATCH liburing 4/4] man: document clock id and IORING_ENTER_ABS_TIMER Pavel Begunkov
2024-08-18 19:39 ` [PATCH liburing 0/4] Tests for absolute timeouts and clockids Jens Axboe
2024-08-18 19:40 ` 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