From: Paolo Abeni <[email protected]>
To: Dylan Yudaken <[email protected]>, Jens Axboe <[email protected]>,
Pavel Begunkov <[email protected]>,
[email protected], [email protected], [email protected],
[email protected]
Cc: [email protected], [email protected]
Subject: Re: [PATCH for-next 0/3] io_uring: multishot recvmsg
Date: Tue, 12 Jul 2022 11:18:33 +0200 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On Fri, 2022-07-08 at 11:43 -0700, Dylan Yudaken wrote:
> This series adds multishot support to recvmsg in io_uring.
>
> The idea is that you submit a single multishot recvmsg and then receive
> completions as and when data arrives. For recvmsg each completion also has
> control data, and this is necessarily included in the same buffer as the
> payload.
>
> In order to do this a new structure is used: io_uring_recvmsg_out. This
> specifies the length written of the name, control and payload. As well as
> including the flags.
> The layout of the buffer is <header><name><control><payload> where the
> lengths are those specified in the original msghdr used to issue the recvmsg.
>
> I suspect this API will be the most contentious part of this series and would
> appreciate any comments on it.
>
> For completeness I considered having the original struct msghdr as the header,
> but size wise it is much bigger (72 bytes including an iovec vs 16 bytes here).
> Testing also showed a 1% slowdown in terms of QPS.
>
> Using a mini network tester [1] shows 14% QPS improvment using this API, however
> this is likely to go down to ~8% with the latest allocation cache added by Jens.
>
> I have based this on this other patch series [2].
>
> [1]: https://github.com/DylanZA/netbench/tree/main
> [2]: https://lore.kernel.org/io-uring/[email protected]/
>
> Dylan Yudaken (3):
> net: copy from user before calling __copy_msghdr
> net: copy from user before calling __get_compat_msghdr
> io_uring: support multishot in recvmsg
>
> include/linux/socket.h | 7 +-
> include/net/compat.h | 5 +-
> include/uapi/linux/io_uring.h | 7 ++
> io_uring/net.c | 195 ++++++++++++++++++++++++++++------
> io_uring/net.h | 5 +
> net/compat.c | 39 +++----
> net/socket.c | 37 +++----
> 7 files changed, 215 insertions(+), 80 deletions(-)
>
>
> base-commit: 9802dee74e7f30ab52dc5f346373185cd860afab
I read the above as this series is targeting Jens's tree. It looks like
it should be conflicts-free vs net-next.
For the network bits:
Acked-by: Paolo Abeni <[email protected]>
Cheers,
Paolo
prev parent reply other threads:[~2022-07-12 9:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-08 18:43 [PATCH for-next 0/3] io_uring: multishot recvmsg Dylan Yudaken
2022-07-08 18:43 ` [PATCH for-next 1/3] net: copy from user before calling __copy_msghdr Dylan Yudaken
2022-07-08 18:43 ` [PATCH for-next 2/3] net: copy from user before calling __get_compat_msghdr Dylan Yudaken
2022-07-08 18:43 ` [PATCH for-next 3/3] io_uring: reintroduce multishot recvmsg Dylan Yudaken
2022-07-08 18:43 ` [PATCH for-next 3/3] io_uring: support multishot in recvmsg Dylan Yudaken
2022-07-12 9:18 ` Paolo Abeni [this message]
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=88f9133542d0a4bf2100e0a521f6e6a19eb2feb1.camel@redhat.com \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[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