From: Hao Xu <[email protected]>
To: Jens Axboe <[email protected]>, io-uring <[email protected]>
Cc: Pavel Begunkov <[email protected]>
Subject: Re: [PATCH] io_uring: read/readv must commit ring mapped buffers upfront
Date: Thu, 16 Jun 2022 12:41:11 +0800 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 6/16/22 09:55, Jens Axboe wrote:
> For recv/recvmsg, IO either completes immediately or gets queued for a
> retry. This isn't the case for read/readv, if eg a normal file or a block
> device is used. Here, an operation can get queued with the block layer.
> If this happens, ring mapped buffers must get committed immediately to
> avoid that the next read can consume the same buffer.
>
> Add an io_op_def flag for this, buffer_ring_commit. If set, when a mapped
> buffer is selected, it is immediately committed.
>
> Fixes: c7fb19428d67 ("io_uring: add support for ring mapped supplied buffers")
> Signed-off-by: Jens Axboe <[email protected]>
>
> ---
>
> diff --git a/fs/io_uring.c b/fs/io_uring.c
> index 5d479428d8e5..05703bcf73fd 100644
> --- a/fs/io_uring.c
> +++ b/fs/io_uring.c
> @@ -1098,6 +1098,8 @@ struct io_op_def {
> unsigned poll_exclusive : 1;
> /* op supports buffer selection */
> unsigned buffer_select : 1;
> + /* op needs immediate commit of ring mapped buffers */
> + unsigned buffer_ring_commit : 1;
> /* do prep async if is going to be punted */
> unsigned needs_async_setup : 1;
> /* opcode is not supported by this kernel */
> @@ -1122,6 +1124,7 @@ static const struct io_op_def io_op_defs[] = {
> .unbound_nonreg_file = 1,
> .pollin = 1,
> .buffer_select = 1,
> + .buffer_ring_commit = 1,
> .needs_async_setup = 1,
> .plug = 1,
> .audit_skip = 1,
> @@ -1239,6 +1242,7 @@ static const struct io_op_def io_op_defs[] = {
> .unbound_nonreg_file = 1,
> .pollin = 1,
> .buffer_select = 1,
> + .buffer_ring_commit = 1,
> .plug = 1,
> .audit_skip = 1,
> .ioprio = 1,
This way we also commit the buffer for read(sockfd) unconditionally.
Would it be better to commit buffer only for read(reg/blk fd) ?
> @@ -3836,7 +3840,8 @@ static void __user *io_ring_buffer_select(struct io_kiocb *req, size_t *len,
> req->buf_list = bl;
> req->buf_index = buf->bid;
>
> - if (issue_flags & IO_URING_F_UNLOCKED) {
> + if (issue_flags & IO_URING_F_UNLOCKED ||
> + io_op_defs[req->opcode].buffer_ring_commit) {
> /*
> * If we came in unlocked, we have no choice but to consume the
> * buffer here. This does mean it'll be pinned until the IO
>
next prev parent reply other threads:[~2022-06-16 4:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-16 1:55 [PATCH] io_uring: read/readv must commit ring mapped buffers upfront Jens Axboe
2022-06-16 4:41 ` Hao Xu [this message]
2022-06-16 11:14 ` Jens Axboe
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 \
[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