From: Ming Lei <ming.lei@redhat.com>
To: Yufen Yu <yuyufen@huawei.com>
Cc: axboe@kernel.dk, linux-block@vger.kernel.org, hch@lst.de,
ming.lei@redhat.com
Subject: Re: [PATCH] blk-mq: run queue after issuing the last request of the plug list
Date: Tue, 19 Jul 2022 17:26:17 +0800 [thread overview]
Message-ID: <YtZ4uSRqR/kLdqm+@T590> (raw)
In-Reply-To: <20220718123528.178714-1-yuyufen@huawei.com>
On Mon, Jul 18, 2022 at 08:35:28PM +0800, Yufen Yu wrote:
> We do test on a virtio scsi device (/dev/sda) and the default mq
> scheduler is 'none'. We found a IO hung as following:
>
> blk_finish_plug
> blk_mq_plug_issue_direct
> scsi_mq_get_budget
> //get budget_token fail and sdev->restarts=1
>
> scsi_end_request
> scsi_run_queue_async
> //sdev->restart=0 and run queue
>
> blk_mq_request_bypass_insert
> //add request to hctx->dispatch list
Here the issue shouldn't be related with scsi's get budget or
scsi_run_queue_async.
If blk-mq adds request into ->dispatch_list, it is blk-mq core's
responsibility to re-run queue for moving on. Can you investigate a
bit more why blk-mq doesn't run queue after adding request to
hctx dispatch list?
Thanks,
Ming
next prev parent reply other threads:[~2022-07-19 9:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-18 12:35 [PATCH] blk-mq: run queue after issuing the last request of the plug list Yufen Yu
2022-07-19 9:26 ` Ming Lei [this message]
2022-07-19 11:00 ` Yufen Yu
2022-07-23 2:50 ` Yu Kuai
2022-07-25 15:43 ` Ming Lei
2022-07-26 1:08 ` Yu Kuai
2022-07-26 1:46 ` Ming Lei
2022-07-26 2:08 ` Yu Kuai
2022-07-26 2:32 ` Ming Lei
2022-07-26 2:52 ` Yu Kuai
2022-07-26 3:02 ` Ming Lei
2022-07-26 3:14 ` Yu Kuai
2022-07-26 3:21 ` Ming Lei
2022-07-26 3:31 ` Yufen Yu
2022-07-26 3:31 ` Yu Kuai
2022-07-26 4:16 ` Ming Lei
2022-07-26 5:01 ` Yufen Yu
2022-07-26 7:39 ` Ming Lei
2022-07-26 9:20 ` Yufen Yu
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=YtZ4uSRqR/kLdqm+@T590 \
--to=ming.lei@redhat.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=yuyufen@huawei.com \
/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