diff options
author | Li Lingfeng <lilingfeng3@huawei.com> | 2023-08-10 06:51:11 +0300 |
---|---|---|
committer | Jens Axboe <axboe@kernel.dk> | 2023-08-10 16:20:31 +0300 |
commit | 4eb44d10766ac0fae5973998fd2a0103df1d3fe1 (patch) | |
tree | 2580c861923412ef148897924352d347cdec321a /block/bfq-wf2q.c | |
parent | c8659bbb15cd42577a9b16a23b527436b028c8b2 (diff) | |
download | linux-4eb44d10766ac0fae5973998fd2a0103df1d3fe1.tar.xz |
block: remove init_mutex and open-code blk_iolatency_try_init
Commit a13696b83da4 ("blk-iolatency: Make initialization lazy") adds
a mutex named "init_mutex" in blk_iolatency_try_init for the race
condition of initializing RQ_QOS_LATENCY.
Now a new lock has been add to struct request_queue by commit a13bd91be223
("block/rq_qos: protect rq_qos apis with a new lock"). And it has been
held in blkg_conf_open_bdev before calling blk_iolatency_init.
So it's not necessary to keep init_mutex in blk_iolatency_try_init, just
remove it.
Since init_mutex has been removed, blk_iolatency_try_init can be
open-coded back to iolatency_set_limit() like ioc_qos_write().
Signed-off-by: Li Lingfeng <lilingfeng3@huawei.com>
Reviewed-by: Michal Koutný <mkoutny@suse.com>
Link: https://lore.kernel.org/r/20230810035111.2236335-1-lilingfeng@huaweicloud.com
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'block/bfq-wf2q.c')
0 files changed, 0 insertions, 0 deletions