qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: xiezhide <xiezhide@huawei.com>
To: qemu-devel@nongnu.org
Cc: groug@kaod.org, aneesh.kumar@linux.vnet.ibm.com,
	eblake@redhat.com, armbru@redhat.com, berto@igalia.com,
	zengcanfu@huawei.com, jinxuefeng@huawei.com,
	johnny.chenyi@huawei.com
Subject: [Qemu-devel] [PATCH v2 0/3] fsdev-throttle-qmp: qmp interface for fsdev io throttling
Date: Tue, 13 Nov 2018 20:12:32 +0800	[thread overview]
Message-ID: <cover.1542110461.git.xiezhide@huawei.com> (raw)

This patches provide qmp interface to query/set io throttle parameters of a fsdev.
Some of patches also refactor the code and structure that was present in block and fsdev files. 

xiezhide (3):
  fsdev-throttle-qmp: refactor code for qmp interface for io throttling
  fsdev-throttle-qmp: qmp interface for fsdev io throttling
  fsdev-throttle-qmp: hmp interface for fsdev io throttling

 Makefile                        |  20 +++-
 Makefile.objs                   |   8 ++
 block/throttle.c                |   6 +-
 blockdev.c                      |  96 +----------------
 fsdev/qemu-fsdev-dummy.c        |  11 ++
 fsdev/qemu-fsdev-throttle.c     | 144 +++++++++++++++++---------
 fsdev/qemu-fsdev-throttle.h     |   6 +-
 fsdev/qemu-fsdev.c              |  29 ++++++
 hmp-commands-info.hx            |  15 +++
 hmp-commands.hx                 |  15 +++
 hmp.c                           |  83 +++++++++++++--
 hmp.h                           |   4 +
 include/qemu/throttle-options.h |   3 +-
 include/qemu/throttle.h         |   4 +-
 include/qemu/typedefs.h         |   1 +
 monitor.c                       |  41 ++++----
 qapi/block-core.json            | 122 +---------------------
 qapi/fsdev.json                 |  96 +++++++++++++++++
 qapi/qapi-schema.json           |   1 +
 qapi/tlimits.json               |  89 ++++++++++++++++
 qmp.c                           |  12 +++
 util/throttle.c                 | 224 ++++++++++++++++++++++++++--------------
 22 files changed, 654 insertions(+), 376 deletions(-)
 create mode 100644 qapi/fsdev.json
 create mode 100644 qapi/tlimits.json

 v0 -> v1:
  Addressed comments from Eric Blake and Greg Kurz.
  Fix patch corrupt issue due to email client change the patch format with copy-to-paster
  Break patch to patches

 v1 -> v2:
  Addressed comments from Greg Kurz.
  send patch with outlook,patch corrupted, resend with git send-email

-- 
2.7.4

             reply	other threads:[~2018-11-13 12:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-13 12:12 xiezhide [this message]
2018-11-13 12:12 ` [Qemu-devel] [PATCH v2 1/3] fsdev-throttle-qmp: refactor code for qmp interface for io throttling xiezhide
2018-11-13 23:25   ` Eric Blake
2018-11-14  8:31     ` xiezhide
2018-11-13 12:13 ` [Qemu-devel] [PATCH v2 2/3] fsdev-throttle-qmp: qmp interface for fsdev " xiezhide
2018-11-13 12:13 ` [Qemu-devel] [PATCH v2 3/3] fsdev-throttle-qmp: hmp " xiezhide
2018-11-13 22:52 ` [Qemu-devel] [PATCH v2 0/3] fsdev-throttle-qmp: qmp " no-reply
2018-11-13 23:03 ` no-reply

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=cover.1542110461.git.xiezhide@huawei.com \
    --to=xiezhide@huawei.com \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=armbru@redhat.com \
    --cc=berto@igalia.com \
    --cc=eblake@redhat.com \
    --cc=groug@kaod.org \
    --cc=jinxuefeng@huawei.com \
    --cc=johnny.chenyi@huawei.com \
    --cc=qemu-devel@nongnu.org \
    --cc=zengcanfu@huawei.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 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).