From: Kevin Wolf <kwolf@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: Max Reitz <mreitz@redhat.com>, Eric Blake <eblake@redhat.com>,
qemu-block@nongnu.org, qemu-devel@nongnu.org, berto@igalia.com
Subject: Re: [Qemu-devel] blockdev-add I/O throttling parameters
Date: Mon, 20 Feb 2017 16:45:54 +0100 [thread overview]
Message-ID: <20170220154554.GF4814@noname.redhat.com> (raw)
In-Reply-To: <20170220153012.GK21255@stefanha-x1.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1143 bytes --]
Am 20.02.2017 um 16:30 hat Stefan Hajnoczi geschrieben:
> I/O throttling parameters are missing from blockdev-add. Is this
> intentional?
>
> I can imagine two solutions that do not need these parameters in
> blockdev-add:
>
> 1. I/O throttling is implemented by a BlockDriver. Users are expected
> to create the BDS themselves. This is a little awkward since
> query-block *does* include the throttling parameters in its output
> and we must preserve this behavior for existing users.
>
> 2. block_set_io_throttle must be used after blockdev-add. Suboptimal
> because issuing two commands is not atomic (use transaction?).
>
> Thoughts?
The existing I/O throttling code is working on BlockBackends, but
blockdev-add creates BlockDriverStates. So it can't possibly add
throttling parameters.
The currently recommended solution block_set_io_throttle. The other
option to control BB level thorttling would be to add qdev properties to
the block devices.
In the long term, I think going with 1. and moving throttling to the
block node level is the much nicer (and more flexible) option.
Kevin
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2017-02-20 15:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-20 15:30 [Qemu-devel] blockdev-add I/O throttling parameters Stefan Hajnoczi
2017-02-20 15:45 ` Kevin Wolf [this message]
2017-02-20 16:29 ` Alberto Garcia
2017-02-21 11:17 ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
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=20170220154554.GF4814@noname.redhat.com \
--to=kwolf@redhat.com \
--cc=berto@igalia.com \
--cc=eblake@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--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.