From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Ming Lei <ming.lei@redhat.com>
Cc: stable@vger.kernel.org, Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org
Subject: Re: [PATCH 6.1 -stable] ublk: remove check IO_URING_F_SQE128 in ublk_ch_uring_cmd
Date: Sun, 27 Aug 2023 11:10:16 +0200 [thread overview]
Message-ID: <2023082709-whisking-pruning-28d0@gregkh> (raw)
In-Reply-To: <20230824052203.1751458-1-ming.lei@redhat.com>
On Thu, Aug 24, 2023 at 01:22:03PM +0800, Ming Lei wrote:
> commit 9c7c4bc986932218fd0df9d2a100509772028fb1 upstream
>
> sizeof(struct ublksrv_io_cmd) is 16bytes, which can be held in 64byte SQE,
> so not necessary to check IO_URING_F_SQE128.
>
> With this change, we get chance to save half SQ ring memory.
>
> Fixed: 71f28f3136af ("ublk_drv: add io_uring based userspace block driver")
> Signed-off-by: Ming Lei <ming.lei@redhat.com>
> Link: https://lore.kernel.org/r/20230220041413.1524335-1-ming.lei@redhat.com
> Signed-off-by: Jens Axboe <axboe@kernel.dk>
> ---
> drivers/block/ublk_drv.c | 3 ---
> 1 file changed, 3 deletions(-)
>
> diff --git a/drivers/block/ublk_drv.c b/drivers/block/ublk_drv.c
> index f48d213fb65e..09d29fa53939 100644
> --- a/drivers/block/ublk_drv.c
> +++ b/drivers/block/ublk_drv.c
> @@ -1271,9 +1271,6 @@ static int ublk_ch_uring_cmd(struct io_uring_cmd *cmd, unsigned int issue_flags)
> __func__, cmd->cmd_op, ub_cmd->q_id, tag,
> ub_cmd->result);
>
> - if (!(issue_flags & IO_URING_F_SQE128))
> - goto out;
> -
> if (ub_cmd->q_id >= ub->dev_info.nr_hw_queues)
> goto out;
>
> --
> 2.40.1
>
Now queued up, thanks.
greg k-h
prev parent reply other threads:[~2023-08-27 9:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-24 5:22 [PATCH 6.1 -stable] ublk: remove check IO_URING_F_SQE128 in ublk_ch_uring_cmd Ming Lei
2023-08-27 9:10 ` Greg Kroah-Hartman [this message]
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=2023082709-whisking-pruning-28d0@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=stable@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.