All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: "Benoît Canet" <benoit@irqsave.net>
Cc: kwolf@redhat.com, stefanha@gmail.com, qemu-devel@nongnu.org,
	stefanha@redhat.com, pbonzini@redhat.com
Subject: Re: [Qemu-devel] [PATCH V8 4/5] block: Add support for throttling burst max in QMP and the command line.
Date: Fri, 30 Aug 2013 14:21:40 -0600	[thread overview]
Message-ID: <5220FED4.6040801@redhat.com> (raw)
In-Reply-To: <1377873389-9712-5-git-send-email-benoit@irqsave.net>

[-- Attachment #1: Type: text/plain, Size: 1747 bytes --]

On 08/30/2013 08:36 AM, Benoît Canet wrote:
> 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.
> 
> Signed-off-by: Benoit Canet <benoit@irqsave.net>
> ---

> @@ -1404,10 +1404,16 @@ Arguments:
>  - "device": device name (json-string)
>  - "bps":  total throughput limit in bytes per second(json-int)
>  - "bps_rd":  read throughput limit in bytes per second(json-int)
> -- "bps_wr":  read throughput limit in bytes per second(json-int)
> +- "bps_wr":  write throughput limit in bytes per second (json-int)

It's odd that you are fixing one pre-existing case of missing space, but
not all of them.  Should we split the cleanups into a separate patch?  I
already started some cleanups[1], but could respin my patch to cover
more, if desired.

> @@ -1417,7 +1423,13 @@ Example:
>                                                 "bps_wr": "0",
>                                                 "iops": "0",
>                                                 "iops_rd": "0",
> -                                               "iops_wr": "0" } }
> +                                               "iops_wr": "0",

Depending on whether my patch[1] goes in first, fix this to use '0'
instead of '"0"'.

[1] still waiting for it to hit
https://lists.gnu.org/archive/html/qemu-devel/2013-08/threads.html, but
message id <1377891353-10682-1-git-send-email-eblake@redhat.com> [PATCH]
qmp: fix integer usage in examples

-- 
Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 621 bytes --]

  reply	other threads:[~2013-08-30 20:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-30 14:36 [Qemu-devel] [PATCH V8 0/5] Continuous Leaky Bucket Throttling Benoît Canet
2013-08-30 14:36 ` [Qemu-devel] [PATCH V8 1/5] throttle: Add a new throttling API implementing continuous leaky bucket Benoît Canet
2013-08-30 14:36 ` [Qemu-devel] [PATCH V8 2/5] throttle: Add units tests Benoît Canet
2013-08-30 14:36 ` [Qemu-devel] [PATCH V8 3/5] block: Enable the new throttling code in the block layer Benoît Canet
2013-08-30 14:36 ` [Qemu-devel] [PATCH V8 4/5] block: Add support for throttling burst max in QMP and the command line Benoît Canet
2013-08-30 20:21   ` Eric Blake [this message]
2013-08-30 20:37     ` Benoît Canet
2013-08-30 20:39       ` Eric Blake
2013-08-30 20:56     ` Benoît Canet
2013-08-30 14:36 ` [Qemu-devel] [PATCH V8 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=5220FED4.6040801@redhat.com \
    --to=eblake@redhat.com \
    --cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.