From: Eric Blake <eblake@redhat.com>
To: Pradeep Jagadeesh <pradeepkiruvale@gmail.com>,
greg kurz <groug@kaod.org>
Cc: Pradeep Jagadeesh <pradeep.jagadeesh@huawei.com>,
Markus Armbruster <armbru@redhat.com>,
alberto garcia <berto@igalia.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
jani kokkonen <jani.kokkonen@huawei.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH V8 5/6] fsdev: QMP interface for throttling
Date: Mon, 7 Aug 2017 07:44:55 -0500 [thread overview]
Message-ID: <8d3843e5-3e6e-84fc-c568-521603abb4c2@redhat.com> (raw)
In-Reply-To: <1502109458-31251-6-git-send-email-pradeep.jagadeesh@huawei.com>
[-- Attachment #1: Type: text/plain, Size: 1452 bytes --]
On 08/07/2017 07:37 AM, Pradeep Jagadeesh wrote:
> This patch introduces 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>
> ---
> Makefile | 4 +++
> fsdev/qemu-fsdev-dummy.c | 11 ++++++
> fsdev/qemu-fsdev-throttle.c | 76 ++++++++++++++++++++++++++++++++++++++++
> fsdev/qemu-fsdev-throttle.h | 8 +++--
> fsdev/qemu-fsdev.c | 38 ++++++++++++++++++++
> monitor.c | 5 +++
> qapi-schema.json | 3 ++
> qapi/fsdev.json | 84 +++++++++++++++++++++++++++++++++++++++++++++
> qmp.c | 14 ++++++++
> 9 files changed, 241 insertions(+), 2 deletions(-)
> create mode 100644 qapi/fsdev.json
>
> +##
> +# @fsdev-set-io-throttle:
> +#
> +# Change I/O limits for a 9p/fsdev device.
> +#
> +# I/O limits can be enabled by setting throttle value to non-zero number.
> +#
> +# I/O limits can be disabled by setting all throttle values to 0.
> +#
> +# Returns: Nothing on success
> +# If @device is not a valid fsdev device, GenericError
> +#
> +# Since: 2.10
> +#
2.11, now.
--
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:45 UTC|newest]
Thread overview: 12+ 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
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 [this message]
2017-08-07 12:46 ` Pradeep Jagadeesh
2017-08-07 12:37 ` [Qemu-devel] [PATCH V8 6/6] fsdev: hmp " 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=8d3843e5-3e6e-84fc-c568-521603abb4c2@redhat.com \
--to=eblake@redhat.com \
--cc=armbru@redhat.com \
--cc=berto@igalia.com \
--cc=dgilbert@redhat.com \
--cc=groug@kaod.org \
--cc=jani.kokkonen@huawei.com \
--cc=pradeep.jagadeesh@huawei.com \
--cc=pradeepkiruvale@gmail.com \
--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).