在 2021/12/10 18:21, Paolo Valente 写道:
Il giorno 27 nov 2021, alle ore 11:11, Yu Kuai<yukuai3@xxxxxxxxxx> ha scritto:
Currently 'num_groups_with_pending_reqs' won't be decreased when
the group doesn't have any pending requests, while any child group
have any pending requests. The decrement is delayed to when all the
child groups doesn't have any pending requests.
For example:
1) t1 issue sync io on root group, t2 and t3 issue sync io on the same
child group. num_groups_with_pending_reqs is 2 now.
2) t1 stopped, num_groups_with_pending_reqs is still 2. io from t2 and
t3 still can't be handled concurrently.
Fix the problem by decreasing 'num_groups_with_pending_reqs'
immediately upon the deactivation of last entity of the group.
I don't understand this patch clearly.
I understand your proposal not to count a group as with pending requests, in case no child process of the group has IO, but only its child groups have pending requests.
So, entities here are only queues for this patch?
If they are only queues, I think it is still incorrect to remove the group from the count of groups with pending IO when all its child queues are deactivated, because there may still be unfinished IO for those queues.
Hi, Paolo
bfq_weights_tree_remove() will be called when all requests are completed
in bfq_queue, thus I recored how many queues have pending requests
through weights tree insertion and removal.(Details in patch 7)
Thus when calling bfq_weights_tree_remove() for bfqq, I can check if
there are no queues have pending requests for parent bfqg:
if (!bfqg->num_entities_with_pending_reqs && -> no queues with pending reqs
entity->in_groups_with_pending_reqs) { -> the group is counted
Thanks,
Kuai
Am I missing something?
Thanks,
Paolo
