qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Lieven <pl@kamp.de>
To: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	qemu block <qemu-block@nongnu.org>
Subject: block/throttle and burst bucket
Date: Thu, 25 Feb 2021 18:34:48 +0100	[thread overview]
Message-ID: <efe8ee1c-e12f-b739-b9dd-9bd6d80527cb@kamp.de> (raw)

Hi,


I was wondering if there is a way to check from outside (qmp etc.) if a throttled block device has exceeded the iops_max_length seconds of time bursting up to iops_max and is now hard limited to the iops limit that is supplied?


Would it be also a good idea to exetend the accounting to account for requests that must have waited before being sent out to the backend device?


Thanks,

Peter




             reply	other threads:[~2021-02-25 17:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-25 17:34 Peter Lieven [this message]
2021-02-26  9:27 ` block/throttle and burst bucket Alberto Garcia
2021-02-26 12:33   ` Peter Lieven
2021-03-01 10:59     ` Kevin Wolf
2021-03-01 12:11       ` Peter Lieven
2021-03-08 12:20         ` Alberto Garcia

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=efe8ee1c-e12f-b739-b9dd-9bd6d80527cb@kamp.de \
    --to=pl@kamp.de \
    --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).