From: Jens Axboe <axboe@kernel.dk>
To: Ming Lei <ming.lei@redhat.com>
Cc: linux-block@vger.kernel.org,
Dongli Zhang <dongli.zhang@oracle.com>,
Christoph Hellwig <hch@infradead.org>,
"Ewan D . Milne" <emilne@redhat.com>
Subject: Re: [PATCH V2] blk-mq: insert passthrough request into hctx->dispatch directly
Date: Mon, 24 Feb 2020 18:51:02 -0700 [thread overview]
Message-ID: <b59035c5-aa41-88a8-d5ae-c53242b59e28@kernel.dk> (raw)
In-Reply-To: <20200225010432.29225-1-ming.lei@redhat.com>
On 2/24/20 6:04 PM, Ming Lei wrote:
> For some reason, device may be in one situation which can't handle
> FS request, so STS_RESOURCE is always returned and the FS request
> will be added to hctx->dispatch. However passthrough request may
> be required at that time for fixing the problem. If passthrough
> request is added to scheduler queue, there isn't any chance for
> blk-mq to dispatch it given we prioritize requests in hctx->dispatch.
> Then the FS IO request may never be completed, and IO hang is caused.
>
> So passthrough request has to be added to hctx->dispatch directly
> for fixing the IO hang.
>
> Fix this issue by inserting passthrough request into hctx->dispatch
> directly together withing adding FS request to the tail of
> hctx->dispatch in blk_mq_dispatch_rq_list(). Actually we add FS request
> to tail of hctx->dispatch at default, see blk_mq_request_bypass_insert().
>
> Then it becomes consistent with original legacy IO request
> path, in which passthrough request is always added to q->queue_head.
Applied, thanks Ming.
--
Jens Axboe
next prev parent reply other threads:[~2020-02-25 1:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-25 1:04 [PATCH V2] blk-mq: insert passthrough request into hctx->dispatch directly Ming Lei
2020-02-25 1:51 ` Jens Axboe [this message]
2020-02-25 15:51 ` Christoph Hellwig
2020-02-25 21:22 ` Ming Lei
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=b59035c5-aa41-88a8-d5ae-c53242b59e28@kernel.dk \
--to=axboe@kernel.dk \
--cc=dongli.zhang@oracle.com \
--cc=emilne@redhat.com \
--cc=hch@infradead.org \
--cc=linux-block@vger.kernel.org \
--cc=ming.lei@redhat.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