diff options
| author |   Douglas Anderson <dianders@chromium.org> | 2020-04-20 09:24:51 -0700 |
|---|---|---|
| committer |   Jens Axboe <axboe@kernel.dk> | 2020-04-20 10:34:56 -0600 |
| commit | ab3cee3762e5e69f27c302c43691289fdfc12316 (patch) | |
| tree | 500a636042931747e63ebf897b47b549b79bbd05 /block/blk-mq-sched.c | |
| parent | Linux 5.7-rc2 (diff) | |
| download | linux-dev-ab3cee3762e5e69f27c302c43691289fdfc12316.tar.xz linux-dev-ab3cee3762e5e69f27c302c43691289fdfc12316.zip | |
blk-mq: In blk_mq_dispatch_rq_list() "no budget" is a reason to kick
In blk_mq_dispatch_rq_list(), if blk_mq_sched_needs_restart() returns
true and the driver returns BLK_STS_RESOURCE then we'll kick the
queue. However, there's another case where we might need to kick it.
If we were unable to get budget we can be in much the same state as
when the driver returns BLK_STS_RESOURCE, so we should treat it the
same.
It should be noted that even if we add a whole bunch of extra kicking
to the queue in other patches this patch is still important.
Specifically any kicking that happened before we re-spliced leftover
requests into 'hctx->dispatch' wouldn't have found any work, so we
really need to make sure we kick ourselves after we've done the
splicing.
Signed-off-by: Douglas Anderson <dianders@chromium.org>
Reviewed-by: Ming Lei <ming.lei@redhat.com>
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'block/blk-mq-sched.c')
0 files changed, 0 insertions, 0 deletions