summaryrefslogtreecommitdiff
path: root/block/blk-timeout.c
diff options
context:
space:
mode:
authorOmar Sandoval <osandov@fb.com>2017-02-22 21:58:30 +0300
committerJens Axboe <axboe@fb.com>2017-02-23 21:55:47 +0300
commitd38d35155514ceef5efb79f6d5b4f0f1638da5b4 (patch)
treeea9eb2e3a10f286ec6813026d6a52a4483602cd4 /block/blk-timeout.c
parentda55f2cc78418dee88400aafbbaed19d7ac8188e (diff)
downloadlinux-d38d35155514ceef5efb79f6d5b4f0f1638da5b4.tar.xz
blk-mq-sched: separate mark hctx and queue restart operations
In blk_mq_sched_dispatch_requests(), we call blk_mq_sched_mark_restart() after we dispatch requests left over on our hardware queue dispatch list. This is so we'll go back and dispatch requests from the scheduler. In this case, it's only necessary to restart the hardware queue that we are running; there's no reason to run other hardware queues just because we are using shared tags. So, split out blk_mq_sched_mark_restart() into two operations, one for just the hardware queue and one for the whole request queue. The core code only needs the hctx variant, but I/O schedulers will want to use both. This also requires adjusting blk_mq_sched_restart_queues() to always check the queue restart flag, not just when using shared tags. Signed-off-by: Omar Sandoval <osandov@fb.com> Signed-off-by: Jens Axboe <axboe@fb.com>
Diffstat (limited to 'block/blk-timeout.c')
0 files changed, 0 insertions, 0 deletions