linux.git/io_uring/rw.h, branch v6.9 Linux kernel source tree io_uring/rw: add separate prep handler for fixed read/write 2023-11-06T14:43:16+00:00 Jens Axboe axboe@kernel.dk 2023-11-06T14:43:16+00:00 f688944cfb810986c626cb13d95bc666e5c8a36c Rather than sprinkle opcode checks in the generic read/write prep handler, have a separate prep handler for the vectored readv/writev operation. Signed-off-by: Jens Axboe <axboe@kernel.dk> 
Rather than sprinkle opcode checks in the generic read/write prep handler,
have a separate prep handler for the vectored readv/writev operation.

Signed-off-by: Jens Axboe <axboe@kernel.dk>
io_uring/rw: add separate prep handler for readv/writev 2023-11-06T14:41:17+00:00 Jens Axboe axboe@kernel.dk 2023-11-06T14:41:17+00:00 0e984ec88da9747549227900e5215c5e6a1b65ae Rather than sprinkle opcode checks in the generic read/write prep handler, have a separate prep handler for the vectored readv/writev operation. Signed-off-by: Jens Axboe <axboe@kernel.dk> 
Rather than sprinkle opcode checks in the generic read/write prep handler,
have a separate prep handler for the vectored readv/writev operation.

Signed-off-by: Jens Axboe <axboe@kernel.dk>
io_uring/rw: add support for IORING_OP_READ_MULTISHOT 2023-09-21T18:02:30+00:00 Jens Axboe axboe@kernel.dk 2023-09-11T19:35:42+00:00 fc68fcda049108478ee4704d8a3ad3e05cc72fd0 This behaves like IORING_OP_READ, except: 1) It only supports pollable files (eg pipes, sockets, etc). Note that for sockets, you probably want to use recv/recvmsg with multishot instead. 2) It supports multishot mode, meaning it will repeatedly trigger a read and fill a buffer when data is available. This allows similar use to recv/recvmsg but on non-sockets, where a single request will repeatedly post a CQE whenever data is read from it. 3) Because of #2, it must be used with provided buffers. This is uniformly true across any request type that supports multishot and transfers data, with the reason being that it's obviously not possible to pass in a single buffer for the data, as multiple reads may very well trigger before an application has a chance to process previous CQEs and the data passed from them. Reviewed-by: Gabriel Krisman Bertazi <krisman@suse.de> Signed-off-by: Jens Axboe <axboe@kernel.dk> 
This behaves like IORING_OP_READ, except:

1) It only supports pollable files (eg pipes, sockets, etc). Note that
   for sockets, you probably want to use recv/recvmsg with multishot
   instead.

2) It supports multishot mode, meaning it will repeatedly trigger a
   read and fill a buffer when data is available. This allows similar
   use to recv/recvmsg but on non-sockets, where a single request will
   repeatedly post a CQE whenever data is read from it.

3) Because of #2, it must be used with provided buffers. This is
   uniformly true across any request type that supports multishot and
   transfers data, with the reason being that it's obviously not
   possible to pass in a single buffer for the data, as multiple reads
   may very well trigger before an application has a chance to process
   previous CQEs and the data passed from them.

Reviewed-by: Gabriel Krisman Bertazi <krisman@suse.de>
Signed-off-by: Jens Axboe <axboe@kernel.dk>
io_uring: avoid indirect function calls for the hottest task_work 2023-06-02T14:55:37+00:00 Jens Axboe axboe@kernel.dk 2023-06-02T14:41:46+00:00 c92fcfc2bab54451c4f1481755ea244f413455cb We use task_work for a variety of reasons, but doing completions or triggering rety after poll are by far the hottest two. Use the indirect funtion call wrappers to avoid the indirect function call if CONFIG_RETPOLINE is set. Signed-off-by: Jens Axboe <axboe@kernel.dk> 
We use task_work for a variety of reasons, but doing completions or
triggering rety after poll are by far the hottest two. Use the indirect
funtion call wrappers to avoid the indirect function call if
CONFIG_RETPOLINE is set.

Signed-off-by: Jens Axboe <axboe@kernel.dk>
io_uring/rw: don't lose partial IO result on fail 2022-09-21T19:15:02+00:00 Pavel Begunkov asml.silence@gmail.com 2022-09-21T11:17:47+00:00 47b4c68660752facfa6247b1fc9ca9d722b8b601 A partially done read/write may end up in io_req_complete_failed() and loose the result, make sure we return the number of bytes processed. Cc: stable@vger.kernel.org Signed-off-by: Pavel Begunkov <asml.silence@gmail.com> Link: https://lore.kernel.org/r/05e0879c226bcd53b441bf92868eadd4bf04e2fc.1663668091.git.asml.silence@gmail.com Signed-off-by: Jens Axboe <axboe@kernel.dk> 
A partially done read/write may end up in io_req_complete_failed() and
loose the result, make sure we return the number of bytes processed.

Cc: stable@vger.kernel.org
Signed-off-by: Pavel Begunkov <asml.silence@gmail.com>
Link: https://lore.kernel.org/r/05e0879c226bcd53b441bf92868eadd4bf04e2fc.1663668091.git.asml.silence@gmail.com
Signed-off-by: Jens Axboe <axboe@kernel.dk>
io_uring: move read/write related opcodes to its own file 2022-07-25T00:39:12+00:00 Jens Axboe axboe@kernel.dk 2022-06-13T13:27:03+00:00 f3b44f92e59a804cf375479bda0bccbf4b6e6ef6 Signed-off-by: Jens Axboe <axboe@kernel.dk> 
Signed-off-by: Jens Axboe <axboe@kernel.dk>