summaryrefslogtreecommitdiff
path: root/block/blk-mq-sched.c
diff options
context:
space:
mode:
authorKemeng Shi <shikemeng@huaweicloud.com>2023-01-18 17:37:24 +0800
committerJens Axboe <axboe@kernel.dk>2023-02-06 09:22:29 -0700
commitf1ce99f7098d9e7a322caf48eb8af05be7999827 (patch)
tree5667778fce8610397787fcefbf937fce24976d22 /block/blk-mq-sched.c
parent4ea58fe456c21bb259a7cbf8498946f86e9b84aa (diff)
blk-mq: remove set of bd->last when get driver tag for next request fails
Commit 113285b473824 ("blk-mq: ensure that bd->last is always set correctly") will set last if we failed to get driver tag for next request to avoid flush miss as we break the list walk and will not send the last request in the list which will be sent with last set normally. This code seems stale now becase the flush introduced is always redundant as: For case tag is really out, we will send a extra flush if we find list is not empty after list walk. For case some tag is freed before retry in blk_mq_prep_dispatch_rq for next, then we can get a tag for next request in retry and flush notified already is not necessary. Just remove these stale codes. Signed-off-by: Kemeng Shi <shikemeng@huaweicloud.com> Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'block/blk-mq-sched.c')
0 files changed, 0 insertions, 0 deletions