All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Fiona Ebner <f.ebner@proxmox.com>
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org, hreitz@redhat.com,
	jsnow@redhat.com
Subject: Re: [PATCH] hw/block/block: add 'throttle-group' property
Date: Tue, 24 Feb 2026 15:34:52 +0100	[thread overview]
Message-ID: <aZ23DELMG6CycbQ8@redhat.com> (raw)
In-Reply-To: <20260116143946.1031006-1-f.ebner@proxmox.com>

Am 16.01.2026 um 15:39 hat Fiona Ebner geschrieben:
> With '-drive', it is possible to specify the throttle configuration
> directly on the commandline. Add the possibility to do the same when
> using the modern way with '-blockdev' and a front-end device. Using a
> throttle filter block node is not always an option: in particular, the
> mirror block job operates on a root block node and it might be desired
> to throttle only the guest IO, but not to the block job.

Hm, is there still a reason why we require a root node for the source?

> There already is a 'block_set_io_throttle' QMP command, but it's nicer
> to be able to do it via the commandline too.
> 
> Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
> ---
> 
> Hope I didn't miss a way to do this already.
> 
> Should changing via qom-set be supported? Currently, an attempt fails:
> > Error: Attempt to set property 'throttle-group' on device 'scsi0'
> > (type 'scsi-hd') after it was realized
> but there already is the 'block_set_io_throttle' QMP command.

It would be nice, but I don't think runtime writable properties are used
much in devices because I believe this would have to be done with plain
QOM properties, i.e. outside of qdev.

Though if it's actually easy, we could consider implementing it.

>  hw/block/block.c           | 15 +++++++++++++++
>  include/hw/block/block.h   |  4 +++-
>  tests/qemu-iotests/172.out | 38 ++++++++++++++++++++++++++++++++++++++
>  3 files changed, 56 insertions(+), 1 deletion(-)

Looks good to me, though maybe we could also use a qemu-iotests case
that actually tries to set the property instead of only updating the
output everywhere for having no throttle group.

Kevin



  parent reply	other threads:[~2026-02-24 14:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-16 14:39 [PATCH] hw/block/block: add 'throttle-group' property Fiona Ebner
2026-02-10  9:22 ` Fiona Ebner
2026-02-24 14:34 ` Kevin Wolf [this message]
2026-02-26 15:20   ` Fiona Ebner
2026-02-26 16:31     ` Kevin Wolf
2026-03-02 12:54       ` Fiona Ebner
2026-03-04 13:02         ` Kevin Wolf
2026-03-04 14:08           ` Fiona Ebner

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=aZ23DELMG6CycbQ8@redhat.com \
    --to=kwolf@redhat.com \
    --cc=f.ebner@proxmox.com \
    --cc=hreitz@redhat.com \
    --cc=jsnow@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 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.