From: Jens Axboe <axboe@kernel.dk>
To: Christoph Hellwig <hch@lst.de>
Cc: linux-block@vger.kernel.org, Damien Le Moal <dlemoal@kernel.org>
Subject: Re: [PATCH 1/5] blk-mq: cleanup __blk_mq_sched_dispatch_requests
Date: Thu, 13 Apr 2023 06:55:19 -0600 [thread overview]
Message-ID: <01f05cb1-fb29-0181-f66f-4b400fec8306@kernel.dk> (raw)
In-Reply-To: <20230413060651.694656-2-hch@lst.de>
On 4/13/23 12:06?AM, Christoph Hellwig wrote:
> __blk_mq_sched_dispatch_requests currently has duplicated logic
> for the cases where requests are on the hctx dispatch list or not.
> Merge the two with a new need_dispatch variable and remove a few
> pointless local variables.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---
> block/blk-mq-sched.c | 31 ++++++++++++++-----------------
> 1 file changed, 14 insertions(+), 17 deletions(-)
>
> diff --git a/block/blk-mq-sched.c b/block/blk-mq-sched.c
> index 06b312c691143f..f3257e1607a00c 100644
> --- a/block/blk-mq-sched.c
> +++ b/block/blk-mq-sched.c
> @@ -271,9 +271,7 @@ static int blk_mq_do_dispatch_ctx(struct blk_mq_hw_ctx *hctx)
>
> static int __blk_mq_sched_dispatch_requests(struct blk_mq_hw_ctx *hctx)
> {
> - struct request_queue *q = hctx->queue;
> - const bool has_sched = q->elevator;
> - int ret = 0;
> + bool need_dispatch = false;
> LIST_HEAD(rq_list);
>
> /*
> @@ -302,23 +300,22 @@ static int __blk_mq_sched_dispatch_requests(struct blk_mq_hw_ctx *hctx)
> */
> if (!list_empty(&rq_list)) {
> blk_mq_sched_mark_restart_hctx(hctx);
> - if (blk_mq_dispatch_rq_list(hctx, &rq_list, 0)) {
> - if (has_sched)
> - ret = blk_mq_do_dispatch_sched(hctx);
> - else
> - ret = blk_mq_do_dispatch_ctx(hctx);
> - }
> - } else if (has_sched) {
> - ret = blk_mq_do_dispatch_sched(hctx);
> - } else if (hctx->dispatch_busy) {
> - /* dequeue request one by one from sw queue if queue is busy */
> - ret = blk_mq_do_dispatch_ctx(hctx);
> + if (!blk_mq_dispatch_rq_list(hctx, &rq_list, 0))
There's some trailing whitespace here. Patch 5 also doesn't seem to
apply, but I'll see what that's about and comment there if there's a
concern.
--
Jens Axboe
next prev parent reply other threads:[~2023-04-13 12:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-13 6:06 cleanup blk_mq_run_hw_queue v2 Christoph Hellwig
2023-04-13 6:06 ` [PATCH 1/5] blk-mq: cleanup __blk_mq_sched_dispatch_requests Christoph Hellwig
2023-04-13 6:23 ` Damien Le Moal
2023-04-13 12:55 ` Jens Axboe [this message]
2023-04-13 6:06 ` [PATCH 2/5] blk-mq: remove the blk_mq_hctx_stopped check in blk_mq_run_work_fn Christoph Hellwig
2023-04-13 6:24 ` Damien Le Moal
2023-04-13 6:06 ` [PATCH 3/5] blk-mq: move the blk_mq_hctx_stopped check in __blk_mq_delay_run_hw_queue Christoph Hellwig
2023-04-13 6:26 ` Damien Le Moal
2023-04-13 6:06 ` [PATCH 4/5] blk-mq: move the !async handling out of __blk_mq_delay_run_hw_queue Christoph Hellwig
2023-04-13 6:06 ` [PATCH 5/5] blk-mq: remove __blk_mq_run_hw_queue Christoph Hellwig
2023-04-13 6:27 ` Damien Le Moal
2023-04-13 13:11 ` cleanup blk_mq_run_hw_queue v2 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=01f05cb1-fb29-0181-f66f-4b400fec8306@kernel.dk \
--to=axboe@kernel.dk \
--cc=dlemoal@kernel.org \
--cc=hch@lst.de \
--cc=linux-block@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox