[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <27f219d07e4e4ce4bfb3263d8d94eae6@AcuMS.aculab.com>
Date: Thu, 14 Jul 2022 07:46:10 +0000
From: David Laight <David.Laight@...LAB.COM>
To: 'Dylan Yudaken' <dylany@...com>, Jens Axboe <axboe@...nel.dk>,
"Pavel Begunkov" <asml.silence@...il.com>,
"davem@...emloft.net" <davem@...emloft.net>,
"edumazet@...gle.com" <edumazet@...gle.com>,
"kuba@...nel.org" <kuba@...nel.org>,
"pabeni@...hat.com" <pabeni@...hat.com>,
"io-uring@...r.kernel.org" <io-uring@...r.kernel.org>
CC: "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"Kernel-team@...com" <Kernel-team@...com>
Subject: RE: [PATCH v2 for-next 3/3] io_uring: support multishot in recvmsg
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)
Powered by blists - more mailing lists