From: Breno Leitao <[email protected]>
To: [email protected], [email protected]
Cc: [email protected]
Subject: [PATCH 0/5] liburing: Add {g,s}etsockopt command support
Date: Fri, 20 Oct 2023 06:39:12 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
These are liburing patches that add support for the new
SOCKET_URING_OP_GETSOCKOPT and SOCKET_URING_OP_SETSOCKOPT socket
commands.
This patchset basically synchronize the UAPI bits, teach
io_uring_prep_cmd(3) how to use the new fields, create a unit test and
add the proper man page documentation.
Breno Leitao (5):
io_uring: uapi: Sync the {g,s}etsockopt fields
liburing.h: Populate SQE for {s,g} etsockopt
tests/socket-getsetsock-cmd: New test for {g,s}etsockopt
man/io_uring_prep_cmd: Fix argument name
man/io_uring_prep_cmd: Add the new sockopt commands
CHANGELOG | 4 +
man/io_uring_prep_cmd.3 | 34 +++-
src/include/liburing.h | 11 +-
src/include/liburing/io_uring.h | 8 +
test/Makefile | 1 +
test/socket-getsetsock-cmd.c | 328 ++++++++++++++++++++++++++++++++
6 files changed, 378 insertions(+), 8 deletions(-)
create mode 100644 test/socket-getsetsock-cmd.c
--
2.34.1
next reply other threads:[~2023-10-20 13:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-20 13:39 Breno Leitao [this message]
2023-10-20 13:39 ` [PATCH 1/5] io_uring: uapi: Sync the {g,s}etsockopt fields Breno Leitao
2023-10-20 13:39 ` [PATCH 2/5] liburing.h: Populate SQE for {s,g} etsockopt Breno Leitao
2023-10-20 13:39 ` [PATCH 3/5] tests/socket-getsetsock-cmd: New test for {g,s}etsockopt Breno Leitao
2023-10-20 13:39 ` [PATCH 4/5] man/io_uring_prep_cmd: Fix argument name Breno Leitao
2023-10-20 13:39 ` [PATCH 5/5] man/io_uring_prep_cmd: Add the new sockopt commands Breno Leitao
2023-10-20 15:06 ` [PATCH 0/5] liburing: Add {g,s}etsockopt command support 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] \
[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