summaryrefslogtreecommitdiff
path: root/block/blk-mq-pci.c
diff options
context:
space:
mode:
authorPaolo Valente <paolo.valente@linaro.org>2021-08-02 16:13:52 +0200
committerJens Axboe <axboe@kernel.dk>2021-09-02 06:36:58 -0600
commit2d52c58b9c9bdae0ca3df6a1eab5745ab3f7d80b (patch)
tree2b7f1c47daa86d0fd4625ff14c4d2b0a3004d837 /block/blk-mq-pci.c
parent55a51ea14094a1e7dd0d7f33237d246033dd39ab (diff)
block, bfq: honor already-setup queue merges
The function bfq_setup_merge prepares the merging between two bfq_queues, say bfqq and new_bfqq. To this goal, it assigns bfqq->new_bfqq = new_bfqq. Then, each time some I/O for bfqq arrives, the process that generated that I/O is disassociated from bfqq and associated with new_bfqq (merging is actually a redirection). In this respect, bfq_setup_merge increases new_bfqq->ref in advance, adding the number of processes that are expected to be associated with new_bfqq. Unfortunately, the stable-merging mechanism interferes with this setup. After bfqq->new_bfqq has been set by bfq_setup_merge, and before all the expected processes have been associated with bfqq->new_bfqq, bfqq may happen to be stably merged with a different queue than the current bfqq->new_bfqq. In this case, bfqq->new_bfqq gets changed. So, some of the processes that have been already accounted for in the ref counter of the previous new_bfqq will not be associated with that queue. This creates an unbalance, because those references will never be decremented. This commit fixes this issue by reestablishing the previous, natural behaviour: once bfqq->new_bfqq has been set, it will not be changed until all expected redirections have occurred. Signed-off-by: Davide Zini <davidezini2@gmail.com> Signed-off-by: Paolo Valente <paolo.valente@linaro.org> Link: https://lore.kernel.org/r/20210802141352.74353-2-paolo.valente@linaro.org Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'block/blk-mq-pci.c')
0 files changed, 0 insertions, 0 deletions