From: Max Reitz <mreitz@redhat.com>
To: Alberto Garcia <berto@igalia.com>, qemu-devel@nongnu.org
Cc: qemu-block@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 2/2] qemu-iotests: Test naming of throttling groups
Date: Fri, 8 Jul 2016 16:31:22 +0200 [thread overview]
Message-ID: <e014fca8-2796-ea8c-d3e7-5caf21bac6ee@redhat.com> (raw)
In-Reply-To: <d87d02823a6b91609509d8bb18e2f5dbd9a6102c.1467986342.git.berto@igalia.com>
[-- Attachment #1: Type: text/plain, Size: 637 bytes --]
On 08.07.2016 16:03, Alberto Garcia wrote:
> Throttling groups are named using the 'group' parameter of the
> block_set_io_throttle command and the throttling.group command-line
> option. If that parameter is unspecified the groups get the name of
> the block device.
>
> This patch adds a new test to check the naming of throttling groups.
>
> Signed-off-by: Alberto Garcia <berto@igalia.com>
> ---
> tests/qemu-iotests/093 | 98 ++++++++++++++++++++++++++++++++++++++++++++++
> tests/qemu-iotests/093.out | 4 +-
> 2 files changed, 100 insertions(+), 2 deletions(-)
Reviewed-by: Max Reitz <mreitz@redhat.com>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 498 bytes --]
next prev parent reply other threads:[~2016-07-08 14:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-08 14:02 [Qemu-devel] [PATCH 0/2] Fix regression with the default naming of throttling groups Alberto Garcia
2016-07-08 14:03 ` [Qemu-devel] [PATCH 1/2] blockdev: " Alberto Garcia
2016-07-08 14:23 ` Max Reitz
2016-07-08 14:25 ` Alberto Garcia
2016-07-08 14:03 ` [Qemu-devel] [PATCH 2/2] qemu-iotests: Test " Alberto Garcia
2016-07-08 14:31 ` Max Reitz [this message]
2016-07-08 14:36 ` [Qemu-devel] [PATCH 0/2] Fix regression with the default " Max Reitz
2016-07-08 16:29 ` 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=e014fca8-2796-ea8c-d3e7-5caf21bac6ee@redhat.com \
--to=mreitz@redhat.com \
--cc=berto@igalia.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 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).