From: Stefano Garzarella <sgarzare@redhat.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: linux-kernel@vger.kernel.org, io-uring@vger.kernel.org
Subject: [PATCH liburing v2 4/5] man/io_uring_register.2: add IORING_CQ_EVENTFD_DISABLED description
Date: Wed, 20 May 2020 19:07:13 +0200 [thread overview]
Message-ID: <20200520170714.68156-5-sgarzare@redhat.com> (raw)
In-Reply-To: <20200520170714.68156-1-sgarzare@redhat.com>
Signed-off-by: Stefano Garzarella <sgarzare@redhat.com>
---
man/io_uring_register.2 | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/man/io_uring_register.2 b/man/io_uring_register.2
index e64f688..5022c03 100644
--- a/man/io_uring_register.2
+++ b/man/io_uring_register.2
@@ -168,6 +168,14 @@ must contain a pointer to the eventfd file descriptor, and
.I nr_args
must be 1. Available since 5.2.
+An application can temporarily disable notifications, coming through the
+registered eventfd, by setting the
+.B IORING_CQ_EVENTFD_DISABLED
+bit in the
+.I flags
+field of the CQ ring.
+Available since 5.8.
+
.TP
.B IORING_REGISTER_EVENTFD_ASYNC
This works just like
--
2.25.4
next prev parent reply other threads:[~2020-05-20 17:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-20 17:07 [PATCH liburing v2 0/5] liburing: add helpers to enable/disable eventfd notifications Stefano Garzarella
2020-05-20 17:07 ` [PATCH liburing v2 1/5] Add CQ ring 'flags' field Stefano Garzarella
2020-05-20 17:07 ` [PATCH liburing v2 2/5] man/io_uring_setup.2: add 'flags' field in the struct io_cqring_offsets Stefano Garzarella
2020-05-20 17:07 ` [PATCH liburing v2 3/5] Add helpers to set and get eventfd notification status Stefano Garzarella
2020-05-20 17:07 ` Stefano Garzarella [this message]
2020-05-20 17:07 ` [PATCH liburing v2 5/5] Add test/eventfd-disable.c test case Stefano Garzarella
2020-05-20 17:12 ` [PATCH liburing v2 0/5] liburing: add helpers to enable/disable eventfd notifications 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 \
--in-reply-to=20200520170714.68156-5-sgarzare@redhat.com \
--to=sgarzare@redhat.com \
--cc=axboe@kernel.dk \
--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;
as well as URLs for NNTP newsgroup(s).