From: Usama Arif <[email protected]>
To: [email protected], [email protected], [email protected]
Cc: [email protected], Usama Arif <[email protected]>
Subject: [RFC 0/3] io_uring: add support for IORING_OP_MSGSND/IORING_OP_MSGRCV
Date: Mon, 13 Jun 2022 20:26:39 +0100 [thread overview]
Message-ID: <[email protected]> (raw)
The first patch just refractors the do_msg function so that its different
parts can be used in io_uring.
The last 2 patches add the support for the async msgsnd/msgrcv.
For msgsnd the pointer to the loaded msgbuf is saved in
io_setup_async_msg_msg for the case when the call is punted to async
context.
For msgrcv, the pointer to user-defined buffer is already stored in the
prep function.
The correspoding prep helpers and a simple testcase for these in liburing
are present at https://github.com/uarif1/liburing/commit/17f6685ca398265b54a07ce4246ee344b5390aad.
These patches are currently missing compat support.
If the patches and approach look acceptable to start review,
I can send the next series with compat support included and also add the
man pages in the above liburing patch.
Thanks!
Usama Arif (3):
ipc/msg: split do_msgsnd into functions
io_uring: add support for IORING_OP_MSGSND
io_uring: add support for IORING_OP_MSGRCV
fs/io_uring.c | 152 ++++++++++++++++++++++++++++++++++
include/linux/msg.h | 11 +++
include/uapi/linux/io_uring.h | 2 +
ipc/msg.c | 52 +++++++++---
4 files changed, 205 insertions(+), 12 deletions(-)
--
2.25.1
next reply other threads:[~2022-06-13 20:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-13 19:26 Usama Arif [this message]
2022-06-13 19:26 ` [RFC 1/3] ipc/msg: split do_msgsnd into functions Usama Arif
2022-06-13 19:26 ` [RFC 2/3] io_uring: add support for IORING_OP_MSGSND Usama Arif
2022-06-13 19:26 ` [RFC 3/3] io_uring: add support for IORING_OP_MSGRCV Usama Arif
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