[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <165662117486.56180.16557557417345255423.b4-ty@kernel.dk>
Date: Thu, 30 Jun 2022 14:32:54 -0600
From: Jens Axboe <axboe@...nel.dk>
To: asml.silence@...il.com, dylany@...com, io-uring@...r.kernel.org
Cc: linux-kernel@...r.kernel.org, Kernel-team@...com
Subject: Re: [PATCH v2 for-next 00/12] io_uring: multishot recv
On Thu, 30 Jun 2022 02:12:19 -0700, Dylan Yudaken wrote:
> This series adds support for multishot recv/recvmsg to io_uring.
>
> The idea is that generally socket applications will be continually
> enqueuing a new recv() when the previous one completes. This can be
> improved on by allowing the application to queue a multishot receive,
> which will post completions as and when data is available. It uses the
> provided buffers feature to receive new data into a pool provided by
> the application.
>
> [...]
Applied, thanks!
[01/12] io_uring: allow 0 length for buffer select
(no commit info)
[02/12] io_uring: restore bgid in io_put_kbuf
(no commit info)
[03/12] io_uring: allow iov_len = 0 for recvmsg and buffer select
(no commit info)
[04/12] io_uring: recycle buffers on error
(no commit info)
[05/12] io_uring: clean up io_poll_check_events return values
(no commit info)
[06/12] io_uring: add IOU_STOP_MULTISHOT return code
(no commit info)
[07/12] io_uring: add allow_overflow to io_post_aux_cqe
(no commit info)
[08/12] io_uring: fix multishot poll on overflow
(no commit info)
[09/12] io_uring: fix multishot accept ordering
(no commit info)
[10/12] io_uring: multishot recv
(no commit info)
[11/12] io_uring: fix io_uring_cqe_overflow trace format
(no commit info)
[12/12] io_uring: only trace one of complete or overflow
(no commit info)
Best regards,
--
Jens Axboe
Powered by blists - more mailing lists