From: Caleb Sander Mateos <[email protected]>
To: Keith Busch <[email protected]>
Cc: [email protected], [email protected], [email protected],
[email protected], [email protected],
[email protected], Keith Busch <[email protected]>
Subject: Re: [PATCHv5 06/11] io_uring/rw: move fixed buffer import to issue path
Date: Tue, 25 Feb 2025 12:57:43 -0800 [thread overview]
Message-ID: <CADUfDZqmVX6Vn9euU0v9AvYGdU6BPtR7vEDBgss_8Hiv7WHuZw@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
On Mon, Feb 24, 2025 at 1:31 PM Keith Busch <[email protected]> wrote:
>
> From: Keith Busch <[email protected]>
>
> Registered buffers may depend on a linked command, which makes the prep
> path too early to import. Move to the issue path when the node is
> actually needed like all the other users of fixed buffers.
>
> Signed-off-by: Keith Busch <[email protected]>
> ---
> io_uring/opdef.c | 8 ++++----
> io_uring/rw.c | 43 ++++++++++++++++++++++++++-----------------
> io_uring/rw.h | 4 ++--
> 3 files changed, 32 insertions(+), 23 deletions(-)
>
> diff --git a/io_uring/opdef.c b/io_uring/opdef.c
> index 9344534780a02..5369ae33b5ad9 100644
> --- a/io_uring/opdef.c
> +++ b/io_uring/opdef.c
> @@ -104,8 +104,8 @@ const struct io_issue_def io_issue_defs[] = {
> .iopoll = 1,
> .iopoll_queue = 1,
> .async_size = sizeof(struct io_async_rw),
> - .prep = io_prep_read_fixed,
> - .issue = io_read,
> + .prep = io_prep_read,
> + .issue = io_read_fixed,
> },
> [IORING_OP_WRITE_FIXED] = {
> .needs_file = 1,
> @@ -118,8 +118,8 @@ const struct io_issue_def io_issue_defs[] = {
> .iopoll = 1,
> .iopoll_queue = 1,
> .async_size = sizeof(struct io_async_rw),
> - .prep = io_prep_write_fixed,
> - .issue = io_write,
> + .prep = io_prep_write,
> + .issue = io_write_fixed,
> },
> [IORING_OP_POLL_ADD] = {
> .needs_file = 1,
> diff --git a/io_uring/rw.c b/io_uring/rw.c
> index db24bcd4c6335..5f37fa48fdd9b 100644
> --- a/io_uring/rw.c
> +++ b/io_uring/rw.c
> @@ -348,33 +348,20 @@ int io_prep_writev(struct io_kiocb *req, const struct io_uring_sqe *sqe)
> return io_prep_rwv(req, sqe, ITER_SOURCE);
> }
>
> -static int io_prep_rw_fixed(struct io_kiocb *req, const struct io_uring_sqe *sqe,
> - int ddir)
> +static int io_init_rw_fixed(struct io_kiocb *req, unsigned int issue_flags, int ddir)
> {
> struct io_rw *rw = io_kiocb_to_cmd(req, struct io_rw);
> - struct io_async_rw *io;
> + struct io_async_rw *io = req->async_data;
> int ret;
>
> - ret = io_prep_rw(req, sqe, ddir, false);
> - if (unlikely(ret))
> - return ret;
> + if (io->bytes_done)
> + return 0;
>
> - io = req->async_data;
> ret = io_import_reg_buf(req, &io->iter, rw->addr, rw->len, ddir, 0);
Shouldn't this be passing issue_flags here?
Best,
Caleb
> iov_iter_save_state(&io->iter, &io->iter_state);
> return ret;
> }
>
> -int io_prep_read_fixed(struct io_kiocb *req, const struct io_uring_sqe *sqe)
> -{
> - return io_prep_rw_fixed(req, sqe, ITER_DEST);
> -}
> -
> -int io_prep_write_fixed(struct io_kiocb *req, const struct io_uring_sqe *sqe)
> -{
> - return io_prep_rw_fixed(req, sqe, ITER_SOURCE);
> -}
> -
> /*
> * Multishot read is prepared just like a normal read/write request, only
> * difference is that we set the MULTISHOT flag.
> @@ -1138,6 +1125,28 @@ int io_write(struct io_kiocb *req, unsigned int issue_flags)
> }
> }
>
> +int io_read_fixed(struct io_kiocb *req, unsigned int issue_flags)
> +{
> + int ret;
> +
> + ret = io_init_rw_fixed(req, issue_flags, ITER_DEST);
> + if (ret)
> + return ret;
> +
> + return io_read(req, issue_flags);
> +}
> +
> +int io_write_fixed(struct io_kiocb *req, unsigned int issue_flags)
> +{
> + int ret;
> +
> + ret = io_init_rw_fixed(req, issue_flags, ITER_SOURCE);
> + if (ret)
> + return ret;
> +
> + return io_write(req, issue_flags);
> +}
> +
> void io_rw_fail(struct io_kiocb *req)
> {
> int res;
> diff --git a/io_uring/rw.h b/io_uring/rw.h
> index a45e0c71b59d6..42a491d277273 100644
> --- a/io_uring/rw.h
> +++ b/io_uring/rw.h
> @@ -30,14 +30,14 @@ struct io_async_rw {
> );
> };
>
> -int io_prep_read_fixed(struct io_kiocb *req, const struct io_uring_sqe *sqe);
> -int io_prep_write_fixed(struct io_kiocb *req, const struct io_uring_sqe *sqe);
> int io_prep_readv(struct io_kiocb *req, const struct io_uring_sqe *sqe);
> int io_prep_writev(struct io_kiocb *req, const struct io_uring_sqe *sqe);
> int io_prep_read(struct io_kiocb *req, const struct io_uring_sqe *sqe);
> int io_prep_write(struct io_kiocb *req, const struct io_uring_sqe *sqe);
> int io_read(struct io_kiocb *req, unsigned int issue_flags);
> int io_write(struct io_kiocb *req, unsigned int issue_flags);
> +int io_read_fixed(struct io_kiocb *req, unsigned int issue_flags);
> +int io_write_fixed(struct io_kiocb *req, unsigned int issue_flags);
> void io_readv_writev_cleanup(struct io_kiocb *req);
> void io_rw_fail(struct io_kiocb *req);
> void io_req_rw_complete(struct io_kiocb *req, io_tw_token_t tw);
> --
> 2.43.5
>
next prev parent reply other threads:[~2025-02-25 20:57 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-24 21:31 [PATCHv5 00/11] ublk zero copy support Keith Busch
2025-02-24 21:31 ` [PATCHv5 01/11] io_uring/rsrc: remove redundant check for valid imu Keith Busch
2025-02-25 8:37 ` Ming Lei
2025-02-25 13:13 ` Pavel Begunkov
2025-02-24 21:31 ` [PATCHv5 02/11] io_uring/nop: reuse req->buf_index Keith Busch
2025-02-24 23:30 ` Jens Axboe
2025-02-25 0:02 ` Keith Busch
2025-02-25 8:43 ` Ming Lei
2025-02-25 13:13 ` Pavel Begunkov
2025-02-24 21:31 ` [PATCHv5 03/11] io_uring/net: reuse req->buf_index for sendzc Keith Busch
2025-02-25 8:44 ` Ming Lei
2025-02-25 13:14 ` Pavel Begunkov
2025-02-24 21:31 ` [PATCHv5 04/11] io_uring/nvme: pass issue_flags to io_uring_cmd_import_fixed() Keith Busch
2025-02-25 8:52 ` Ming Lei
2025-02-24 21:31 ` [PATCHv5 05/11] io_uring: combine buffer lookup and import Keith Busch
2025-02-25 8:55 ` Ming Lei
2025-02-24 21:31 ` [PATCHv5 06/11] io_uring/rw: move fixed buffer import to issue path Keith Busch
2025-02-25 9:26 ` Ming Lei
2025-02-25 13:57 ` Pavel Begunkov
2025-02-25 20:57 ` Caleb Sander Mateos [this message]
2025-02-25 21:16 ` Keith Busch
2025-02-24 21:31 ` [PATCHv5 07/11] io_uring: add support for kernel registered bvecs Keith Busch
2025-02-25 9:40 ` Ming Lei
2025-02-25 17:32 ` Keith Busch
2025-02-25 22:47 ` Ming Lei
2025-02-25 22:55 ` Keith Busch
2025-02-25 14:00 ` Pavel Begunkov
2025-02-25 14:05 ` Pavel Begunkov
2025-02-25 20:58 ` Caleb Sander Mateos
2025-02-24 21:31 ` [PATCHv5 08/11] nvme: map uring_cmd data even if address is 0 Keith Busch
2025-02-25 9:41 ` Ming Lei
2025-02-24 21:31 ` [PATCHv5 09/11] ublk: zc register/unregister bvec Keith Busch
2025-02-25 11:00 ` Ming Lei
2025-02-25 16:35 ` Keith Busch
2025-02-25 22:56 ` Ming Lei
2025-02-25 16:19 ` Pavel Begunkov
2025-02-25 16:27 ` Keith Busch
2025-02-25 16:42 ` Pavel Begunkov
2025-02-25 16:52 ` Keith Busch
2025-02-27 4:16 ` Ming Lei
2025-02-25 21:14 ` Caleb Sander Mateos
2025-02-26 8:15 ` Ming Lei
2025-02-26 17:10 ` Keith Busch
2025-02-27 4:19 ` Ming Lei
2025-02-24 21:31 ` [PATCHv5 10/11] io_uring: add abstraction for buf_table rsrc data Keith Busch
2025-02-25 16:04 ` Pavel Begunkov
2025-02-24 21:31 ` [PATCHv5 11/11] io_uring: cache nodes and mapped buffers Keith Busch
2025-02-25 13:11 ` Pavel Begunkov
2025-02-25 14:10 ` [PATCHv5 00/11] ublk zero copy support Pavel Begunkov
2025-02-25 14:47 ` Jens Axboe
2025-02-25 15:07 ` (subset) " 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 \
--in-reply-to=CADUfDZqmVX6Vn9euU0v9AvYGdU6BPtR7vEDBgss_8Hiv7WHuZw@mail.gmail.com \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[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