qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Benoît Canet" <benoit@irqsave.net>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com, stefanha@gmail.com,
	"Benoît Canet" <benoit@irqsave.net>,
	stefanha@redhat.com, pbonzini@redhat.com
Subject: [Qemu-devel] [PATCH V10 0/5] Continuous Leaky Bucket Throttling
Date: Sun,  1 Sep 2013 18:33:07 +0200	[thread overview]
Message-ID: <1378053192-10419-1-git-send-email-benoit@irqsave.net> (raw)

This patchset implement continous leaky bucket throttling.

It use two requests queue to enable to do silly unbalanced throttling like
block_set_io_throttle 0 0 0 0 6000 1

It use two timer to get the timer callbacks and the throttle.c code simple

in this version
   Rebased on top of Eric latest patch (merged in qemu-trivial-next)

v9:
   Apply Reviewed-By by Eric
   Rebased on top of "qmp: fix integer usage in examples" by Eric (Please apply it
first)

v8:

   rearm timer only when it's not pending [Stefan]
   Schedule next request right after accouting it [Stefan]

v7:
   honor max values if specified [Paolo]
   s/cfg/Linux CFQ/ [Stefan]
   revert throttle_get_config to it's old prototype [Stefan]
   s/size/@size/ [Stefan]
   s/acccount/account/ [Stefan]
   remove tracked_request_end uneeded hunk [Stefan]
   Spaces before (json-int)s [Stefan]


Benoît Canet (5):
  throttle: Add a new throttling API implementing continuous leaky
    bucket.
  throttle: Add units tests
  block: Enable the new throttling code in the block layer.
  block: Add support for throttling burst max in QMP and the command
    line.
  block: Add iops_size to do the iops accounting for a given io size.

 block.c                   |  338 +++++++++----------------------
 block/qapi.c              |   50 +++--
 blockdev.c                |  205 ++++++++++++++-----
 hmp.c                     |   36 +++-
 include/block/block.h     |    1 -
 include/block/block_int.h |   32 +--
 include/qemu/throttle.h   |  103 ++++++++++
 qapi-schema.json          |   40 +++-
 qemu-options.hx           |    4 +-
 qmp-commands.hx           |   32 ++-
 tests/Makefile            |    2 +
 tests/test-throttle.c     |  481 +++++++++++++++++++++++++++++++++++++++++++++
 util/Makefile.objs        |    1 +
 util/throttle.c           |  396 +++++++++++++++++++++++++++++++++++++
 14 files changed, 1383 insertions(+), 338 deletions(-)
 create mode 100644 include/qemu/throttle.h
 create mode 100644 tests/test-throttle.c
 create mode 100644 util/throttle.c

-- 
1.7.10.4

             reply	other threads:[~2013-09-01 16:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-01 16:33 Benoît Canet [this message]
2013-09-01 16:33 ` [Qemu-devel] [PATCH V10 1/5] throttle: Add a new throttling API implementing continuous leaky bucket Benoît Canet
2013-09-01 16:33 ` [Qemu-devel] [PATCH V10 2/5] throttle: Add units tests Benoît Canet
2013-09-01 16:33 ` [Qemu-devel] [PATCH V10 3/5] block: Enable the new throttling code in the block layer Benoît Canet
2013-09-01 16:33 ` [Qemu-devel] [PATCH V10 4/5] block: Add support for throttling burst max in QMP and the command line Benoît Canet
2013-09-01 16:33 ` [Qemu-devel] [PATCH V10 5/5] block: Add iops_size to do the iops accounting for a given io size Benoît Canet

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=1378053192-10419-1-git-send-email-benoit@irqsave.net \
    --to=benoit@irqsave.net \
    --cc=kwolf@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.com \
    --cc=stefanha@redhat.com \
    /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).