From: Stefan Hajnoczi <stefanha@gmail.com>
To: Alberto Garcia <berto@igalia.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
qemu-devel@nongnu.org, qemu-block@nongnu.org,
Max Reitz <mreitz@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v9 0/8] Block Throttle Group Support
Date: Fri, 12 Jun 2015 14:01:10 +0100 [thread overview]
Message-ID: <20150612130110.GA30168@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <cover.1433779731.git.berto@igalia.com>
[-- Attachment #1: Type: text/plain, Size: 4018 bytes --]
On Mon, Jun 08, 2015 at 06:17:40PM +0200, Alberto Garcia wrote:
> V9:
> - Make test-throttle.c call bdrv_init() to make sure that
> throttle_groups_init() gets called and the mutex is initialized.
> This was breaking the tests in Mac OS X.
>
> V8: https://lists.gnu.org/archive/html/qemu-devel/2015-05/msg03716.html
> - Rebased against the current master.
>
> V7: https://lists.gnu.org/archive/html/qemu-devel/2015-04/msg01196.html
> - Make block_set_io_throttle() keep a device in the same group if the
> parameter is omitted, and rewrite the code a bit to make it clearer
> and slightly more efficient.
>
> - Update the documentation of block_set_io_throttle() to explain in
> detail how it works.
>
> - Improve the iotest 093 to test scenarios with several devices in the
> same group.
>
> - Update version number to 2.4 in the 'Since:' fields.
>
>
> V6: https://lists.gnu.org/archive/html/qemu-devel/2015-03/msg06036.html
> - Use qemu_init_main_loop() in the throttling tests to make sure that
> all BDS have an AioContext attached.
>
>
> V5: https://lists.gnu.org/archive/html/qemu-devel/2015-03/msg05990.html
> - Fixed and expanded the tests. There's a new one that checks that
> configuration changes affect the whole throttling group.
>
> - Refactored the code a bit: new function schedule_next_request()
>
> - any_timer_armed is now reset in throttle_group_config(), it was
> causing qemu-iotest 093 to fail.
>
> - Documentation improvements
>
>
> V4: https://lists.gnu.org/archive/html/qemu-devel/2015-03/msg05558.html
> - All functions from the ThrottleGroup API now receive a BlockDriverState.
>
> - The creation/destruction of ThrottleTimers is now handled internally.
>
> - bdrv_io_limits_enable() no longer accepts NULL as a valid group name.
>
> - No member of a group can access someone else's throttled_reqs queues
> anymore.
>
> - No member of a group can access someone else's timers unless they
> have queued requests.
>
> - After a timer is fired make sure that there was actually a request
> in the queue, and schedule a new one otherwise.
>
> - Protect bdrv_swap() by locking the throttling group.
>
> - throttle_group_co_io_limits_intercept() is now marked as a coroutine
> function.
>
> - Documentation updates.
>
> Regards,
>
> Berto
>
> Alberto Garcia (7):
> throttle: Add throttle group infrastructure
> throttle: Add throttle group infrastructure tests
> throttle: Add throttle group support
> throttle: acquire the ThrottleGroup lock in bdrv_swap()
> throttle: add the name of the ThrottleGroup to BlockDeviceInfo
> throttle: Update throttle infrastructure copyright
> qemu-iotests: expand test 093 to support group throttling
>
> Benoît Canet (1):
> throttle: Extract timers from ThrottleState into a separate structure
>
> block.c | 38 ++-
> block/Makefile.objs | 1 +
> block/io.c | 71 ++----
> block/qapi.c | 8 +-
> block/throttle-groups.c | 496 ++++++++++++++++++++++++++++++++++++++++
> blockdev.c | 38 ++-
> hmp.c | 10 +-
> include/block/block.h | 3 +-
> include/block/block_int.h | 7 +-
> include/block/throttle-groups.h | 46 ++++
> include/qemu/throttle.h | 46 ++--
> qapi/block-core.json | 29 ++-
> qemu-options.hx | 1 +
> qmp-commands.hx | 3 +-
> tests/qemu-iotests/093 | 89 ++++---
> tests/test-throttle.c | 163 +++++++++----
> util/throttle.c | 81 ++++---
> 17 files changed, 927 insertions(+), 203 deletions(-)
> create mode 100644 block/throttle-groups.c
> create mode 100644 include/block/throttle-groups.h
>
> --
> 2.1.4
>
>
Thanks, applied to my block tree:
https://github.com/stefanha/qemu/commits/block
Stefan
[-- Attachment #2: Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2015-06-12 13:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-08 16:17 [Qemu-devel] [PATCH v9 0/8] Block Throttle Group Support Alberto Garcia
2015-06-08 16:17 ` [Qemu-devel] [PATCH v9 1/8] throttle: Extract timers from ThrottleState into a separate structure Alberto Garcia
2015-06-08 16:17 ` [Qemu-devel] [PATCH v9 2/8] throttle: Add throttle group infrastructure Alberto Garcia
2015-06-08 16:17 ` [Qemu-devel] [PATCH v9 3/8] throttle: Add throttle group infrastructure tests Alberto Garcia
2015-06-08 16:17 ` [Qemu-devel] [PATCH v9 4/8] throttle: Add throttle group support Alberto Garcia
2015-06-08 16:17 ` [Qemu-devel] [PATCH v9 5/8] throttle: acquire the ThrottleGroup lock in bdrv_swap() Alberto Garcia
2015-06-08 16:17 ` [Qemu-devel] [PATCH v9 6/8] throttle: add the name of the ThrottleGroup to BlockDeviceInfo Alberto Garcia
2015-06-08 16:17 ` [Qemu-devel] [PATCH v9 7/8] throttle: Update throttle infrastructure copyright Alberto Garcia
2015-06-08 16:17 ` [Qemu-devel] [PATCH v9 8/8] qemu-iotests: expand test 093 to support group throttling Alberto Garcia
2015-06-12 13:01 ` Stefan Hajnoczi [this message]
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=20150612130110.GA30168@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.com \
--cc=berto@igalia.com \
--cc=kwolf@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 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).