qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: qemu-block@nongnu.org
Cc: kwolf@redhat.com, qemu-devel@nongnu.org
Subject: [Qemu-devel] [PULL 21/34] throttle: Add support for burst periods
Date: Mon, 22 Feb 2016 17:32:39 +0100	[thread overview]
Message-ID: <1456158772-9344-22-git-send-email-kwolf@redhat.com> (raw)
In-Reply-To: <1456158772-9344-1-git-send-email-kwolf@redhat.com>

From: Alberto Garcia <berto@igalia.com>

This patch adds support for burst periods to the throttling code.
With this feature the user can keep performing bursts as defined by
the LeakyBucket.max rate for a configurable period of time.

Signed-off-by: Alberto Garcia <berto@igalia.com>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
---
 include/qemu/throttle.h | 41 +++++++++++++++++++++++----
 util/throttle.c         | 73 ++++++++++++++++++++++++++++++++++++++++---------
 2 files changed, 96 insertions(+), 18 deletions(-)

diff --git a/include/qemu/throttle.h b/include/qemu/throttle.h
index 8ec8951..63df690 100644
--- a/include/qemu/throttle.h
+++ b/include/qemu/throttle.h
@@ -2,7 +2,7 @@
  * QEMU throttling infrastructure
  *
  * Copyright (C) Nodalink, EURL. 2013-2014
- * Copyright (C) Igalia, S.L. 2015
+ * Copyright (C) Igalia, S.L. 2015-2016
  *
  * Authors:
  *   Benoît Canet <benoit.canet@nodalink.com>
@@ -42,16 +42,47 @@ typedef enum {
 } BucketType;
 
 /*
- * The max parameter of the leaky bucket throttling algorithm can be used to
- * allow the guest to do bursts.
- * The max value is a pool of I/O that the guest can use without being throttled
- * at all. Throttling is triggered once this pool is empty.
+ * This module implements I/O limits using the leaky bucket
+ * algorithm. The code is independent of the I/O units, but it is
+ * currently used for bytes per second and operations per second.
+ *
+ * Three parameters can be set by the user:
+ *
+ * - avg: the desired I/O limits in units per second.
+ * - max: the limit during bursts, also in units per second.
+ * - burst_length: the maximum length of the burst period, in seconds.
+ *
+ * Here's how it works:
+ *
+ * - The bucket level (number of performed I/O units) is kept in
+ *   bkt.level and leaks at a rate of bkt.avg units per second.
+ *
+ * - The size of the bucket is bkt.max * bkt.burst_length. Once the
+ *   bucket is full no more I/O is performed until the bucket leaks
+ *   again. This is what makes the I/O rate bkt.avg.
+ *
+ * - The bkt.avg rate does not apply until the bucket is full,
+ *   allowing the user to do bursts until then. The I/O limit during
+ *   bursts is bkt.max. To enforce this limit we keep an additional
+ *   bucket in bkt.burst_length that leaks at a rate of bkt.max units
+ *   per second.
+ *
+ * - Because of all of the above, the user can perform I/O at a
+ *   maximum of bkt.max units per second for at most bkt.burst_length
+ *   seconds in a row. After that the bucket will be full and the I/O
+ *   rate will go down to bkt.avg.
+ *
+ * - Since the bucket always leaks at a rate of bkt.avg, this also
+ *   determines how much the user needs to wait before being able to
+ *   do bursts again.
  */
 
 typedef struct LeakyBucket {
     double  avg;              /* average goal in units per second */
     double  max;              /* leaky bucket max burst in units */
     double  level;            /* bucket level in units */
+    double  burst_level;      /* bucket level in units (for computing bursts) */
+    unsigned burst_length;    /* max length of the burst period, in seconds */
 } LeakyBucket;
 
 /* The following structure is used to configure a ThrottleState
diff --git a/util/throttle.c b/util/throttle.c
index 6a01cee..371c769 100644
--- a/util/throttle.c
+++ b/util/throttle.c
@@ -41,6 +41,14 @@ void throttle_leak_bucket(LeakyBucket *bkt, int64_t delta_ns)
 
     /* make the bucket leak */
     bkt->level = MAX(bkt->level - leak, 0);
+
+    /* if we allow bursts for more than one second we also need to
+     * keep track of bkt->burst_level so the bkt->max goal per second
+     * is attained */
+    if (bkt->burst_length > 1) {
+        leak = (bkt->max * (double) delta_ns) / NANOSECONDS_PER_SECOND;
+        bkt->burst_level = MAX(bkt->burst_level - leak, 0);
+    }
 }
 
 /* Calculate the time delta since last leak and make proportionals leaks
@@ -91,13 +99,24 @@ int64_t throttle_compute_wait(LeakyBucket *bkt)
         return 0;
     }
 
-    extra = bkt->level - bkt->max;
+    /* If the bucket is full then we have to wait */
+    extra = bkt->level - bkt->max * bkt->burst_length;
+    if (extra > 0) {
+        return throttle_do_compute_wait(bkt->avg, extra);
+    }
 
-    if (extra <= 0) {
-        return 0;
+    /* If the bucket is not full yet we have to make sure that we
+     * fulfill the goal of bkt->max units per second. */
+    if (bkt->burst_length > 1) {
+        /* We use 1/10 of the max value to smooth the throttling.
+         * See throttle_fix_bucket() for more details. */
+        extra = bkt->burst_level - bkt->max / 10;
+        if (extra > 0) {
+            return throttle_do_compute_wait(bkt->max, extra);
+        }
     }
 
-    return throttle_do_compute_wait(bkt->avg, extra);
+    return 0;
 }
 
 /* This function compute the time that must be waited while this IO
@@ -177,7 +196,11 @@ void throttle_timers_attach_aio_context(ThrottleTimers *tt,
  */
 void throttle_config_init(ThrottleConfig *cfg)
 {
+    unsigned i;
     memset(cfg, 0, sizeof(*cfg));
+    for (i = 0; i < BUCKETS_COUNT; i++) {
+        cfg->buckets[i].burst_length = 1;
+    }
 }
 
 /* To be called first on the ThrottleState */
@@ -301,6 +324,16 @@ bool throttle_is_valid(ThrottleConfig *cfg, Error **errp)
             return false;
         }
 
+        if (!cfg->buckets[i].burst_length) {
+            error_setg(errp, "the burst length cannot be 0");
+            return false;
+        }
+
+        if (cfg->buckets[i].burst_length > 1 && !cfg->buckets[i].max) {
+            error_setg(errp, "burst length set without burst rate");
+            return false;
+        }
+
         if (cfg->buckets[i].max && !cfg->buckets[i].avg) {
             error_setg(errp, "bps_max/iops_max require corresponding"
                        " bps/iops values");
@@ -317,7 +350,7 @@ static void throttle_fix_bucket(LeakyBucket *bkt)
     double min;
 
     /* zero bucket level */
-    bkt->level = 0;
+    bkt->level = bkt->burst_level = 0;
 
     /* The following is done to cope with the Linux CFQ block scheduler
      * which regroup reads and writes by block of 100ms in the guest.
@@ -420,22 +453,36 @@ bool throttle_schedule_timer(ThrottleState *ts,
  */
 void throttle_account(ThrottleState *ts, bool is_write, uint64_t size)
 {
+    const BucketType bucket_types_size[2][2] = {
+        { THROTTLE_BPS_TOTAL, THROTTLE_BPS_READ },
+        { THROTTLE_BPS_TOTAL, THROTTLE_BPS_WRITE }
+    };
+    const BucketType bucket_types_units[2][2] = {
+        { THROTTLE_OPS_TOTAL, THROTTLE_OPS_READ },
+        { THROTTLE_OPS_TOTAL, THROTTLE_OPS_WRITE }
+    };
     double units = 1.0;
+    unsigned i;
 
     /* if cfg.op_size is defined and smaller than size we compute unit count */
     if (ts->cfg.op_size && size > ts->cfg.op_size) {
         units = (double) size / ts->cfg.op_size;
     }
 
-    ts->cfg.buckets[THROTTLE_BPS_TOTAL].level += size;
-    ts->cfg.buckets[THROTTLE_OPS_TOTAL].level += units;
+    for (i = 0; i < 2; i++) {
+        LeakyBucket *bkt;
+
+        bkt = &ts->cfg.buckets[bucket_types_size[is_write][i]];
+        bkt->level += size;
+        if (bkt->burst_length > 1) {
+            bkt->burst_level += size;
+        }
 
-    if (is_write) {
-        ts->cfg.buckets[THROTTLE_BPS_WRITE].level += size;
-        ts->cfg.buckets[THROTTLE_OPS_WRITE].level += units;
-    } else {
-        ts->cfg.buckets[THROTTLE_BPS_READ].level += size;
-        ts->cfg.buckets[THROTTLE_OPS_READ].level += units;
+        bkt = &ts->cfg.buckets[bucket_types_units[is_write][i]];
+        bkt->level += units;
+        if (bkt->burst_length > 1) {
+            bkt->burst_level += units;
+        }
     }
 }
 
-- 
1.8.3.1

  parent reply	other threads:[~2016-02-22 16:33 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-22 16:32 [Qemu-devel] [PULL 00/34] Block layer patches Kevin Wolf
2016-02-22 16:32 ` [Qemu-devel] [PULL 01/34] qemu-img: initialize MapEntry object Kevin Wolf
2016-02-22 16:32 ` [Qemu-devel] [PULL 02/34] quorum: fix segfault when read fails in fifo mode Kevin Wolf
2016-02-22 16:32 ` [Qemu-devel] [PULL 03/34] spec: add qcow2 bitmaps extension specification Kevin Wolf
2016-02-22 16:32 ` [Qemu-devel] [PULL 04/34] block: Fix -incoming with snapshot=on Kevin Wolf
2016-02-22 16:32 ` [Qemu-devel] [PULL 05/34] qemu-io: add support for --object command line arg Kevin Wolf
2016-02-22 16:32 ` [Qemu-devel] [PULL 06/34] qemu-img: " Kevin Wolf
2016-02-22 16:32 ` [Qemu-devel] [PULL 07/34] qemu-io: allow specifying image as a set of options args Kevin Wolf
2016-02-22 16:32 ` [Qemu-devel] [PULL 08/34] qemu-nbd: " Kevin Wolf
2016-02-22 16:32 ` [Qemu-devel] [PULL 09/34] qemu-img: " Kevin Wolf
2016-02-22 16:32 ` [Qemu-devel] [PULL 10/34] qemu-nbd: don't overlap long option values with short options Kevin Wolf
2016-02-22 16:32 ` [Qemu-devel] [PULL 11/34] qemu-nbd: use no_argument/required_argument constants Kevin Wolf
2016-02-22 16:32 ` [Qemu-devel] [PULL 12/34] qemu-io: " Kevin Wolf
2016-02-22 16:32 ` [Qemu-devel] [PULL 13/34] block migration: Activate image on destination before writing to it Kevin Wolf
2016-02-22 16:32 ` [Qemu-devel] [PULL 14/34] throttle: Make throttle_compute_timer() static Kevin Wolf
2016-02-22 16:32 ` [Qemu-devel] [PULL 15/34] throttle: Make throttle_conflicting() set errp Kevin Wolf
2016-02-22 16:32 ` [Qemu-devel] [PULL 16/34] throttle: Make throttle_max_is_missing_limit() " Kevin Wolf
2016-02-22 16:32 ` [Qemu-devel] [PULL 17/34] throttle: Make throttle_is_valid() " Kevin Wolf
2016-02-22 16:32 ` [Qemu-devel] [PULL 18/34] throttle: Set always an average value when setting a maximum value Kevin Wolf
2016-02-22 16:32 ` [Qemu-devel] [PULL 19/34] throttle: Merge all functions that check the configuration into one Kevin Wolf
2016-02-22 16:32 ` [Qemu-devel] [PULL 20/34] throttle: Use throttle_config_init() to initialize ThrottleConfig Kevin Wolf
2016-02-22 16:32 ` Kevin Wolf [this message]
2016-02-22 16:32 ` [Qemu-devel] [PULL 22/34] throttle: Add command-line settings to define the burst periods Kevin Wolf
2016-02-22 16:32 ` [Qemu-devel] [PULL 23/34] qapi: Add burst length parameters to block_set_io_throttle Kevin Wolf
2016-02-22 16:32 ` [Qemu-devel] [PULL 24/34] qapi: Add burst length fields to BlockDeviceInfo Kevin Wolf
2016-02-22 16:32 ` [Qemu-devel] [PULL 25/34] throttle: Check that burst_level leaks correctly Kevin Wolf
2016-02-22 16:32 ` [Qemu-devel] [PULL 26/34] throttle: Test throttle_compute_wait() during bursts Kevin Wolf
2016-02-22 16:32 ` [Qemu-devel] [PULL 27/34] qemu-iotests: Extend iotest 093 to test bursts Kevin Wolf
2016-02-22 16:32 ` [Qemu-devel] [PULL 28/34] qapi: Correct the name of the iops_rd parameter Kevin Wolf
2016-02-22 16:32 ` [Qemu-devel] [PULL 29/34] docs: Document the throttling infrastructure Kevin Wolf
2016-02-22 16:32 ` [Qemu-devel] [PULL 30/34] MAINTAINERS: Add myself as maintainer of the throttling code Kevin Wolf
2016-02-22 16:32 ` [Qemu-devel] [PULL 31/34] blockdev: unset inappropriate flags when changing medium Kevin Wolf
2016-02-22 16:32 ` [Qemu-devel] [PULL 32/34] qemu-iotests: 067: ignore QMP events Kevin Wolf
2016-02-22 16:32 ` [Qemu-devel] [PULL 33/34] qemu-iotests: 140: don't use IDE device Kevin Wolf
2016-02-22 16:32 ` [Qemu-devel] [PULL 34/34] qemu-iotests: 140: make description slightly more verbose Kevin Wolf
2016-02-22 17:46 ` [Qemu-devel] [PULL 00/34] Block layer patches Peter Maydell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1456158772-9344-22-git-send-email-kwolf@redhat.com \
    --to=kwolf@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).