block, bfq: fix service being wrongly set to zero in case of preemption

If
- a bfq_queue Q preempts another queue, because one request of Q
arrives in time,
- but, after this preemption, Q is not the queue that is set in service,
then Q->entity.service is set to 0 when Q is eventually set in
service. But Q should have continued receiving service with its old
budget (which is why preemption has occurred) and its old service.

This commit addresses this issue by resetting service on queue real
expiration.

Tested-by: Holger Hoffstätte <holger@applied-asynchrony.com>
Tested-by: Oleksandr Natalenko <oleksandr@natalenko.name>
Signed-off-by: Paolo Valente <paolo.valente@linaro.org>
Signed-off-by: Jens Axboe <axboe@kernel.dk>

1 files changed, 28 insertions, 6 deletions

diff --git a/block/bfq-iosched.c b/block/bfq-iosched.c
index 4fd4f1996498..d579cc8e0db6 100644
--- a/block/bfq-iosched.c
+++ b/block/bfq-iosched.c
@@ -1382,18 +1382,30 @@ static bool bfq_bfqq_update_budg_for_activation(struct bfq_data *bfqd,
                  * remain unchanged after such an expiration, and the
                  * following statement therefore assigns to
                  * entity->budget the remaining budget on such an
-                 * expiration. For clarity, entity->service is not
-                 * updated on expiration in any case, and, in normal
-                 * operation, is reset only when bfqq is selected for
-                 * service (see bfq_get_next_queue).
+                 * expiration.
                  */
                 entity->budget = min_t(unsigned long,
                                        bfq_bfqq_budget_left(bfqq),
                                        bfqq->max_budget);
 
+                /*
+                 * At this point, we have used entity->service to get
+                 * the budget left (needed for updating
+                 * entity->budget). Thus we finally can, and have to,
+                 * reset entity->service. The latter must be reset
+                 * because bfqq would otherwise be charged again for
+                 * the service it has received during its previous
+                 * service slot(s).
+                 */
+                entity->service = 0;
+
                 return true;
         }
 
+        /*
+         * We can finally complete expiration, by setting service to 0.
+         */
+        entity->service = 0;
         entity->budget = max_t(unsigned long, bfqq->max_budget,
                                bfq_serv_to_charge(bfqq->next_rq, bfqq));
         bfq_clear_bfqq_non_blocking_wait_rq(bfqq);
@@ -3271,11 +3283,21 @@ void bfq_bfqq_expire(struct bfq_data *bfqd,
         ref = bfqq->ref;
         __bfq_bfqq_expire(bfqd, bfqq);
 
+        if (ref == 1) /* bfqq is gone, no more actions on it */
+                return;
+
         /* mark bfqq as waiting a request only if a bic still points to it */
-        if (ref > 1 && !bfq_bfqq_busy(bfqq) &&
+        if (!bfq_bfqq_busy(bfqq) &&
             reason != BFQQE_BUDGET_TIMEOUT &&
-            reason != BFQQE_BUDGET_EXHAUSTED)
+            reason != BFQQE_BUDGET_EXHAUSTED) {
                 bfq_mark_bfqq_non_blocking_wait_rq(bfqq);
+                /*
+                 * Not setting service to 0, because, if the next rq
+                 * arrives in time, the queue will go on receiving
+                 * service with this same budget (as if it never expired)
+                 */
+        } else
+                entity->service = 0;
 }
 
 /*