From: Dylan Yudaken <[email protected]>
To: <[email protected]>
Cc: <[email protected]>, <[email protected]>, <[email protected]>,
Dylan Yudaken <[email protected]>
Subject: [PATCH v3 liburing 2/7] add IORING_RECV_MULTISHOT to io_uring.h
Date: Thu, 30 Jun 2022 09:49:13 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
copy relevant part from include/uapi/linux/io_uring.h from
for-5.20/io_uring branch
Signed-off-by: Dylan Yudaken <[email protected]>
---
src/include/liburing/io_uring.h | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/src/include/liburing/io_uring.h b/src/include/liburing/io_uring.h
index 0fd1f98..de42c54 100644
--- a/src/include/liburing/io_uring.h
+++ b/src/include/liburing/io_uring.h
@@ -244,8 +244,13 @@ enum io_uring_op {
* or receive and arm poll if that yields an
* -EAGAIN result, arm poll upfront and skip
* the initial transfer attempt.
+ *
+ * IORING_RECV_MULTISHOT Multishot recv. Sets IORING_CQE_F_MORE if
+ * the handler will continue to report
+ * CQEs on behalf of the same SQE.
*/
#define IORING_RECVSEND_POLL_FIRST (1U << 0)
+#define IORING_RECV_MULTISHOT (1U << 1)
/*
* accept flags stored in sqe->ioprio
--
2.30.2
next prev parent reply other threads:[~2022-06-30 16:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-30 16:49 [PATCH v3 liburing 0/7] liburing: multishot receive Dylan Yudaken
2022-06-30 16:49 ` [PATCH v3 liburing 1/7] add t_create_socket_pair Dylan Yudaken
2022-06-30 16:49 ` Dylan Yudaken [this message]
2022-06-30 16:49 ` [PATCH v3 liburing 3/7] add io_uring_prep_(recv|recvmsg)_multishot Dylan Yudaken
2022-06-30 16:49 ` [PATCH v3 liburing 4/7] add IORING_RECV_MULTISHOT docs Dylan Yudaken
2022-06-30 16:49 ` [PATCH v3 liburing 5/7] add recv-multishot test Dylan Yudaken
2022-06-30 16:49 ` [PATCH v3 liburing 6/7] add poll overflow test Dylan Yudaken
2022-06-30 16:49 ` [PATCH v3 liburing 7/7] add accept with " Dylan Yudaken
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