public inbox for [email protected]
 help / color / mirror / Atom feed
From: Anuj gupta <[email protected]>
To: Jens Axboe <[email protected]>
Cc: io-uring <[email protected]>, Kanchan Joshi <[email protected]>
Subject: Re: [PATCH] io_uring/uring_cmd: assign ioucmd->cmd at async prep time
Date: Wed, 5 Apr 2023 21:14:22 +0530	[thread overview]
Message-ID: <CACzX3AtFDJy1LqvrdgfJDie34Z+13eoa-nQ5J97mALzKJiHn2Q@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>

On Wed, Apr 5, 2023 at 7:54 PM Jens Axboe <[email protected]> wrote:
>
> Rather than check this in the fast path issue, it makes more sense to
> just assign the copy of the data when we're setting it up anyway. This
> makes the code a bit cleaner, and removes the need for this check in
> the issue path.
>
> Signed-off-by: Jens Axboe <[email protected]>
>
> ---
>
> diff --git a/io_uring/uring_cmd.c b/io_uring/uring_cmd.c
> index 3d825d939b13..f7a96bc76ea1 100644
> --- a/io_uring/uring_cmd.c
> +++ b/io_uring/uring_cmd.c
> @@ -73,6 +73,7 @@ int io_uring_cmd_prep_async(struct io_kiocb *req)
>         cmd_size = uring_cmd_pdu_size(req->ctx->flags & IORING_SETUP_SQE128);
>
>         memcpy(req->async_data, ioucmd->cmd, cmd_size);
> +       ioucmd->cmd = req->async_data;
>         return 0;
>  }
>
> @@ -129,9 +130,6 @@ int io_uring_cmd(struct io_kiocb *req, unsigned int issue_flags)
>                 WRITE_ONCE(ioucmd->cookie, NULL);
>         }
>
> -       if (req_has_async_data(req))
> -               ioucmd->cmd = req->async_data;
> -
>         ret = file->f_op->uring_cmd(ioucmd, issue_flags);
>         if (ret == -EAGAIN) {
>                 if (!req_has_async_data(req)) {
>
> --
> Jens Axboe
>

Looks good.

Reviewed-by: Anuj Gupta <[email protected]>

  parent reply	other threads:[~2023-04-05 15:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-05 14:23 [PATCH] io_uring/uring_cmd: assign ioucmd->cmd at async prep time Jens Axboe
2023-04-05 14:36 ` Gabriel Krisman Bertazi
2023-04-05 15:29 ` Keith Busch
2023-04-05 15:44 ` Anuj gupta [this message]
2023-04-05 18:00 ` Kanchan Joshi

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=CACzX3AtFDJy1LqvrdgfJDie34Z+13eoa-nQ5J97mALzKJiHn2Q@mail.gmail.com \
    [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