From: Ammar Faizi <ammarfaizi2@gmail.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: io-uring Mailing List <io-uring@vger.kernel.org>,
Pavel Begunkov <asml.silence@gmail.com>,
"David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Ammar Faizi <ammarfaizi2@gmail.com>, Nugra <richiisei@gmail.com>
Subject: [RFC PATCH liburing v1 2/5] io_uring.h: Add `IORING_OP_SENDTO` and `IORING_OP_RECVFROM`
Date: Fri, 31 Dec 2021 00:50:16 +0700 [thread overview]
Message-ID: <20211230174548.178641-3-ammar.faizi@intel.com> (raw)
In-Reply-To: <20211230174548.178641-1-ammar.faizi@intel.com>
Sync with the kernel to support for `sendto(2)` and `recvfrom(2)`,
this adds those two new opcodes.
Signed-off-by: Ammar Faizi <ammarfaizi2@gmail.com>
---
src/include/liburing/io_uring.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/src/include/liburing/io_uring.h b/src/include/liburing/io_uring.h
index 9d8c7f9..47038f6 100644
--- a/src/include/liburing/io_uring.h
+++ b/src/include/liburing/io_uring.h
@@ -154,6 +154,8 @@ enum {
IORING_OP_SETXATTR,
IORING_OP_FGETXATTR,
IORING_OP_GETXATTR,
+ IORING_OP_SENDTO,
+ IORING_OP_RECVFROM,
/* this goes last, obviously */
IORING_OP_LAST,
--
2.32.0
next prev parent reply other threads:[~2021-12-30 17:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-30 17:50 [RFC PATCH liburing v1 0/5] liburing: Add sendto(2) and recvfrom(2) support Ammar Faizi
2021-12-30 17:50 ` [RFC PATCH liburing v1 1/5] .gitignore: Add `/test/xattr` and `/test/getdents` Ammar Faizi
2021-12-30 17:50 ` Ammar Faizi [this message]
2021-12-30 17:50 ` [RFC PATCH liburing v1 3/5] liburing.h: Add `io_uring_prep_{sendto,sendto}` helper Ammar Faizi
2021-12-30 17:50 ` [RFC PATCH liburing v1 4/5] test: Add sendto_recvfrom test program Ammar Faizi
2021-12-30 17:50 ` [RFC PATCH liburing v1 5/5] man: Add `io_uring_prep_{sendto,recvfrom}` docs 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=20211230174548.178641-3-ammar.faizi@intel.com \
--to=ammarfaizi2@gmail.com \
--cc=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=davem@davemloft.net \
--cc=io-uring@vger.kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=richiisei@gmail.com \
/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