From: Greg Kurz <groug@kaod.org>
To: Alberto Garcia <berto@igalia.com>
Cc: Pradeep Jagadeesh <pradeepkiruvale@gmail.com>,
eric blake <eblake@redhat.com>,
Pradeep Jagadeesh <pradeep.jagadeesh@huawei.com>,
Markus Armbruster <armbru@redhat.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
jani kokkonen <jani.kokkonen@huawei.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v8 0/6] fsdev: qmp interface for io throttling
Date: Wed, 30 Aug 2017 16:28:59 +0200 [thread overview]
Message-ID: <20170830162859.16b5a8a3@bahia> (raw)
In-Reply-To: <w51fuc98di8.fsf@maestria.local.igalia.com>
[-- Attachment #1: Type: text/plain, Size: 785 bytes --]
On Wed, 30 Aug 2017 14:07:59 +0200
Alberto Garcia <berto@igalia.com> wrote:
> On Tue 29 Aug 2017 04:23:01 PM CEST, Pradeep Jagadeesh wrote:
> > These patches provide the qmp interface, to query the io throttle
> > status of the all fsdev devices that are present in a vm.
>
> I'm trying to read from an 9p share that has limits set with hmp
> fsdev_set_io_throttle and I'm having some problems.
>
> For example if I'm reading a large file and I change the I/O limits
> while the file is still being read then the guest process freezes.
>
> Can you try to reproduce that scenario?
>
> Berto
Thanks Berto for the review and the testing ! I'm on vacation but I'll
jump in next week when I'm back and Pradeep has posted the next version.
Cheers,
--
Greg
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2017-08-30 14:29 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
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 1/6] throttle: factor out duplicate code Pradeep Jagadeesh
2017-08-29 14:23 ` [Qemu-devel] [PATCH v8 2/6] qmp: Create IOThrottle structure Pradeep Jagadeesh
2017-08-29 14:23 ` [Qemu-devel] [PATCH v8 3/6] throttle: move out function to reuse the code Pradeep Jagadeesh
2017-08-29 14:23 ` [Qemu-devel] [PATCH v8 4/6] hmp: create a throttle initialization function for code reusability Pradeep Jagadeesh
2017-08-29 14:23 ` [Qemu-devel] [PATCH v8 5/6] fsdev: hmp interface for throttling Pradeep Jagadeesh
2017-08-30 9:38 ` Alberto Garcia
2017-09-04 12:22 ` Pradeep Jagadeesh
2017-09-04 13:05 ` Alberto Garcia
2017-08-29 14:23 ` [Qemu-devel] [PATCH v8 6/6] fsdev: QMP " Pradeep Jagadeesh
2017-08-29 14:36 ` [Qemu-devel] [PATCH v8 0/6] fsdev: qmp interface for io throttling Alberto Garcia
2017-08-29 14:39 ` Pradeep Jagadeesh
2017-08-30 12:07 ` Alberto Garcia
2017-08-30 12:10 ` Pradeep Jagadeesh
2017-08-30 14:54 ` Alberto Garcia
2017-08-30 15:07 ` Pradeep Jagadeesh
2017-08-30 15:10 ` Alberto Garcia
2017-08-30 15:12 ` Pradeep Jagadeesh
2017-08-31 13:34 ` Alberto Garcia
2017-08-31 13:39 ` Pradeep Jagadeesh
2017-09-01 12:44 ` Pradeep Jagadeesh
2017-08-30 14:28 ` Greg Kurz [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-08-07 12:37 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=20170830162859.16b5a8a3@bahia \
--to=groug@kaod.org \
--cc=armbru@redhat.com \
--cc=berto@igalia.com \
--cc=dgilbert@redhat.com \
--cc=eblake@redhat.com \
--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).