From: David Laight <David.Laight@ACULAB.COM>
To: 'Dylan Yudaken' <dylany@fb.com>, Jens Axboe <axboe@kernel.dk>,
"Pavel Begunkov" <asml.silence@gmail.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"edumazet@google.com" <edumazet@google.com>,
"kuba@kernel.org" <kuba@kernel.org>,
"pabeni@redhat.com" <pabeni@redhat.com>,
"io-uring@vger.kernel.org" <io-uring@vger.kernel.org>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"Kernel-team@fb.com" <Kernel-team@fb.com>
Subject: RE: [PATCH v2 for-next 3/3] io_uring: support multishot in recvmsg
Date: Thu, 14 Jul 2022 07:46:10 +0000 [thread overview]
Message-ID: <27f219d07e4e4ce4bfb3263d8d94eae6@AcuMS.aculab.com> (raw)
In-Reply-To: <20220713082321.1445020-4-dylany@fb.com>
From: Dylan Yudaken
> Sent: 13 July 2022 09:23
>
> Similar to multishot recv, this will require provided buffers to be
> used. However recvmsg is much more complex than recv as it has multiple
> outputs. Specifically flags, name, and control messages.
...
Why is this any different from adding several 'recvmsg' requests
into the request ring?
IIUC the requests are all processed sequentially by a single thread.
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
next prev parent reply other threads:[~2022-07-14 7:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-13 8:23 [PATCH v2 for-next 0/3] io_uring: multishot recvmsg Dylan Yudaken
2022-07-13 8:23 ` [PATCH v2 for-next 1/3] net: copy from user before calling __copy_msghdr Dylan Yudaken
2022-07-13 8:23 ` [PATCH v2 for-next 2/3] net: copy from user before calling __get_compat_msghdr Dylan Yudaken
2022-07-13 8:23 ` [PATCH v2 for-next 3/3] io_uring: support multishot in recvmsg Dylan Yudaken
2022-07-13 12:48 ` Jens Axboe
2022-07-14 9:11 ` Dylan Yudaken
2022-07-14 7:46 ` David Laight [this message]
2022-07-14 9:20 ` 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 \
--in-reply-to=27f219d07e4e4ce4bfb3263d8d94eae6@AcuMS.aculab.com \
--to=david.laight@aculab.com \
--cc=Kernel-team@fb.com \
--cc=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=davem@davemloft.net \
--cc=dylany@fb.com \
--cc=edumazet@google.com \
--cc=io-uring@vger.kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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