From: "John Stoffel" <john@stoffel.org>
To: Bart Van Assche <Bart.VanAssche@wdc.com>
Cc: "snitzer\@redhat.com" <snitzer@redhat.com>,
"linux-block\@vger.kernel.org" <linux-block@vger.kernel.org>,
"axboe\@kernel.dk" <axboe@kernel.dk>,
"dm-devel\@redhat.com" <dm-devel@redhat.com>,
"linux-nvme\@lists.infradead.org"
<linux-nvme@lists.infradead.org>,
"linux-scsi\@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: [dm-devel] [PATCH V4] blk-mq: introduce BLK_STS_DEV_RESOURCE
Date: Thu, 1 Feb 2018 19:26:34 -0500 [thread overview]
Message-ID: <23155.45114.317289.396546@quad.stoffel.home> (raw)
In-Reply-To: <1517262713.2687.56.camel@wdc.com>
>>>>> "Bart" == Bart Van Assche <Bart.VanAssche@wdc.com> writes:
Bart> On Mon, 2018-01-29 at 16:44 -0500, Mike Snitzer wrote:
>> But regardless of which wins the race, the queue will have been run.
>> Which is all we care about right?
Bart> Running the queue is not sufficient. With this patch applied it can happen
Bart> that the block driver returns BLK_STS_DEV_RESOURCE, that the two or more
Bart> concurrent queue runs finish before sufficient device resources are available
Bart> to execute the request and that blk_mq_delay_run_hw_queue() does not get
Bart> called at all. If no other activity triggers a queue run, e.g. request
Bart> completion, this will result in a queue stall.
Doesn't this argue that you really want some sort of completions to be
run in this case instead? Instead of busy looping or waiting for a
set amount of time, just fire off a callback to run once you have the
resources available, no?
I can't provide any code examples, I don't know the code base nearly
well enough.
John
next prev parent reply other threads:[~2018-02-02 0:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-29 20:33 [PATCH V4] blk-mq: introduce BLK_STS_DEV_RESOURCE Mike Snitzer
2018-01-29 21:22 ` Bart Van Assche
2018-01-29 21:44 ` Mike Snitzer
2018-01-29 21:51 ` Bart Van Assche
2018-01-29 22:14 ` Mike Snitzer
2018-01-29 22:22 ` Bart Van Assche
2018-01-30 5:55 ` [dm-devel] " Ming Lei
2018-01-30 3:20 ` Ming Lei
2018-02-02 0:26 ` John Stoffel [this message]
2018-02-02 0:53 ` [dm-devel] " Bart Van Assche
2018-01-30 3:16 ` 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=23155.45114.317289.396546@quad.stoffel.home \
--to=john@stoffel.org \
--cc=Bart.VanAssche@wdc.com \
--cc=axboe@kernel.dk \
--cc=dm-devel@redhat.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=snitzer@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