From: Ammar Faizi <ammarfaizi2@gnuweeb.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: Ammar Faizi <ammarfaizi2@gnuweeb.org>,
Alviro Iskandar Setiawan <alviro.iskandar@gnuweeb.org>,
GNU/Weeb Mailing List <gwml@vger.gnuweeb.org>,
Christian Mazakas <christian.mazakas@gmail.com>,
io-uring Mailing List <io-uring@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [PATCH liburing 0/3] Manpage updates for iowait toggle feature and one extra FFI fix
Date: Sun, 27 Jul 2025 07:43:13 +0700 [thread overview]
Message-ID: <20250727004316.3351033-1-ammarfaizi2@gnuweeb.org> (raw)
Hi Jens,
As previously discussed on Discord, here are two manpage updates
about the iowait toggle feature. And then I have one extra FFI
trivial fix. The FFI fix is safe to apply for the liburing 2.12
release.
- Add `io_uring_set_iowait(3)` manpage.
- Add `IORING_ENTER_NO_IOWAIT` flag to `io_uring_enter(2)`
- Don't use `IOURINGINLINE` on private helpers in `liburing.h`.
Signed-off-by: Ammar Faizi <ammarfaizi2@gnuweeb.org>
---
Ammar Faizi (3):
man: Add `io_uring_set_iowait(3)`
man: Add `IORING_ENTER_NO_IOWAIT` flag
liburing: Don't use `IOURINGINLINE` on private helpers
man/io_uring_enter.2 | 16 ++++++++++-
man/io_uring_set_iowait.3 | 57 +++++++++++++++++++++++++++++++++++++++
src/include/liburing.h | 6 ++---
3 files changed, 75 insertions(+), 4 deletions(-)
create mode 100644 man/io_uring_set_iowait.3
base-commit: 6d3d27bc42733f5a407424c76aadcc84bd4b0cf0
--
Ammar Faizi
next reply other threads:[~2025-07-27 0:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-27 0:43 Ammar Faizi [this message]
2025-07-27 0:43 ` [PATCH liburing 1/3] man: Add `io_uring_set_iowait(3)` Ammar Faizi
2025-07-27 0:43 ` [PATCH liburing 2/3] man: Add `IORING_ENTER_NO_IOWAIT` flag Ammar Faizi
2025-07-27 0:43 ` [PATCH liburing 3/3] liburing: Don't use `IOURINGINLINE` on private helpers Ammar Faizi
2025-07-27 0:53 ` Ammar Faizi
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=20250727004316.3351033-1-ammarfaizi2@gnuweeb.org \
--to=ammarfaizi2@gnuweeb.org \
--cc=alviro.iskandar@gnuweeb.org \
--cc=axboe@kernel.dk \
--cc=christian.mazakas@gmail.com \
--cc=gwml@vger.gnuweeb.org \
--cc=io-uring@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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