From: Eric Blake <eblake@redhat.com>
To: Pradeep Jagadeesh <pradeepkiruvale@gmail.com>,
greg kurz <groug@kaod.org>
Cc: Pradeep Jagadeesh <pradeep.jagadeesh@huawei.com>,
alberto garcia <berto@igalia.com>,
jani kokkonen <jani.kokkonen@huawei.com>,
qemu-devel@nongnu.org, Manos Pitsidianakis <el13635@mail.ntua.gr>,
qemu block <qemu-block@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH V8 2/6] qmp: Create IOThrottle structure
Date: Mon, 7 Aug 2017 07:44:09 -0500 [thread overview]
Message-ID: <4329dde2-984f-8fcc-8d16-76d55dd9f538@redhat.com> (raw)
In-Reply-To: <1502109458-31251-3-git-send-email-pradeep.jagadeesh@huawei.com>
[-- Attachment #1: Type: text/plain, Size: 2010 bytes --]
On 08/07/2017 07:37 AM, Pradeep Jagadeesh wrote:
> This patch enables qmp interfaces for the fsdev
> devices. This provides two interfaces one
> for querying info of all the fsdev devices. The second one
> to set the IO limits for the required fsdev device.
>
> Signed-off-by: Pradeep Jagadeesh <pradeep.jagadeesh@huawei.com>
> Reviewed-by: Greg Kurz <groug@kaod.org>
> Reviewed-by: Eric Blake <eblake@redhat.com>
> Reviewed-by: Alberto Garcia <berto@igalia.com>
> ---
> qapi/block-core.json | 76 ++-------------------------------------------
> qapi/iothrottle.json | 88 ++++++++++++++++++++++++++++++++++++++++++++++++++++
> 2 files changed, 91 insertions(+), 73 deletions(-)
> create mode 100644 qapi/iothrottle.json
I'm wondering how much of this overlaps or even duplicates Manos'
efforts on making throttling a separate filter BDS.
> +++ b/qapi/iothrottle.json
> @@ -0,0 +1,88 @@
> +# -*- Mode: Python -*-
> +
> +##
> +# == QAPI IOThrottle definitions
> +##
> +
> +##
> +# @IOThrottle:
> +#
> +# A set of parameters describing IO throttling
> +#
> +# @id: The name or QOM path of the guest device (since: 2.8)
> +# Since: 2.10
Also, we've missed freeze for 2.10; this refactoring now belongs in 2.11.
> +##
> +{ 'struct': 'IOThrottle',
> + 'data': { '*id': 'str', 'bps': 'int', 'bps_rd': 'int',
> + 'bps_wr': 'int', 'iops': 'int', 'iops_rd': 'int', 'iops_wr': 'int',
> + '*bps_max': 'int', '*bps_rd_max': 'int',
> + '*bps_wr_max': 'int', '*iops_max': 'int',
> + '*iops_rd_max': 'int', '*iops_wr_max': 'int',
> + '*bps_max_length': 'int', '*bps_rd_max_length': 'int',
> + '*bps_wr_max_length': 'int', '*iops_max_length': 'int',
> + '*iops_rd_max_length': 'int', '*iops_wr_max_length': 'int',
> + '*iops_size': 'int' } }
>
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 619 bytes --]
next prev parent reply other threads:[~2017-08-07 12:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-07 12:37 [Qemu-devel] [PATCH v8 0/6] fsdev: qmp interface for io throttling Pradeep Jagadeesh
2017-08-07 12:37 ` [Qemu-devel] [PATCH V8 1/6] throttle: factor out duplicate code Pradeep Jagadeesh
2017-08-07 12:37 ` [Qemu-devel] [PATCH V8 2/6] qmp: Create IOThrottle structure Pradeep Jagadeesh
2017-08-07 12:44 ` Eric Blake [this message]
2017-08-07 12:37 ` [Qemu-devel] [PATCH V8 3/6] throttle: move out function to reuse the code Pradeep Jagadeesh
2017-08-29 14:30 ` Alberto Garcia
2017-08-07 12:37 ` [Qemu-devel] [PATCH V8 4/6] hmp: create a throttle initialization function for code reusability Pradeep Jagadeesh
2017-08-29 14:22 ` Alberto Garcia
2017-08-07 12:37 ` [Qemu-devel] [PATCH V8 5/6] fsdev: QMP interface for throttling Pradeep Jagadeesh
2017-08-07 12:44 ` Eric Blake
2017-08-07 12:46 ` Pradeep Jagadeesh
2017-08-07 12:37 ` [Qemu-devel] [PATCH V8 6/6] fsdev: hmp " Pradeep Jagadeesh
-- strict thread matches above, loose matches on Subject: below --
2017-08-29 14:23 [Qemu-devel] [PATCH v8 0/6] fsdev: qmp interface for io throttling Pradeep Jagadeesh
2017-08-29 14:23 ` [Qemu-devel] [PATCH v8 2/6] qmp: Create IOThrottle structure Pradeep Jagadeesh
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=4329dde2-984f-8fcc-8d16-76d55dd9f538@redhat.com \
--to=eblake@redhat.com \
--cc=berto@igalia.com \
--cc=el13635@mail.ntua.gr \
--cc=groug@kaod.org \
--cc=jani.kokkonen@huawei.com \
--cc=pradeep.jagadeesh@huawei.com \
--cc=pradeepkiruvale@gmail.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 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).