From: Paolo Bonzini <pbonzini@redhat.com>
To: Andrey Korolyov <andrey@xdel.ru>, Stefan Hajnoczi <stefanha@redhat.com>
Cc: Stefan Hajnoczi <stefanha@gmail.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] dataplane degradation in 2.1
Date: Thu, 10 Jul 2014 18:08:32 +0200 [thread overview]
Message-ID: <53BEBA80.6040000@redhat.com> (raw)
In-Reply-To: <CABYiri8=wJuOXLx9Rpdx4dNnZz8bPYomaqw8apU5=77Puek7Gg@mail.gmail.com>
Il 10/07/2014 17:10, Andrey Korolyov ha scritto:
> Cool, thanks Stefan. Nearly missed this set in patchwork because it
> came a bit earlier than the latest fix addressed to the segfault I
> mentioned. By the way, do you plan to add I/O throttlers to the
> iothread model in next release cycles?
Throttling per-BlockDriverState is already supported by dataplane.
Paolo
prev parent reply other threads:[~2014-07-10 16:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-09 16:50 [Qemu-devel] dataplane degradation in 2.1 Andrey Korolyov
2014-07-10 5:42 ` Fam Zheng
2014-07-10 14:33 ` Andrey Korolyov
2014-07-10 14:39 ` Stefan Hajnoczi
2014-07-10 15:10 ` Andrey Korolyov
2014-07-10 16:08 ` Paolo Bonzini [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=53BEBA80.6040000@redhat.com \
--to=pbonzini@redhat.com \
--cc=andrey@xdel.ru \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--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).