From: Eric Blake <eblake@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>, qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
ming.lei@canonical.com
Subject: Re: [Qemu-devel] [PATCH 2/2] block: bump coroutine pool size for drives
Date: Thu, 03 Jul 2014 08:03:44 -0600 [thread overview]
Message-ID: <53B562C0.6020606@redhat.com> (raw)
In-Reply-To: <1404395521-11158-3-git-send-email-stefanha@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 765 bytes --]
On 07/03/2014 07:52 AM, Stefan Hajnoczi wrote:
> When a BlockDriverState is associated with a storage controller
> DeviceState we expect guest I/O. Use this opportunity to bump the
> coroutine pool size by 64.
>
> This patch ensures that the coroutine pool size scales with the number
> of drives attached to the guest. It should increase coroutine pool
> usage (which makes qemu_coroutine_create() fast) without hogging too
> much memory when fewer drives are attached.
>
> Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
> ---
> block.c | 4 ++++
> 1 file changed, 4 insertions(+)
Reviewed-by: Eric Blake <eblake@redhat.com>
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2014-07-03 14:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-03 13:51 [Qemu-devel] [PATCH 0/2] coroutine: dynamically scale pool size Stefan Hajnoczi
2014-07-03 13:52 ` [Qemu-devel] [PATCH 1/2] coroutine: make pool size dynamic Stefan Hajnoczi
2014-07-03 13:59 ` Eric Blake
2014-07-03 18:29 ` Stefan Hajnoczi
2014-07-03 13:52 ` [Qemu-devel] [PATCH 2/2] block: bump coroutine pool size for drives Stefan Hajnoczi
2014-07-03 14:03 ` Eric Blake [this message]
2014-07-04 5:10 ` [Qemu-devel] [PATCH 0/2] coroutine: dynamically scale pool size Ming Lei
2014-07-04 6:31 ` Paolo Bonzini
2014-07-04 7:02 ` Ming Lei
2014-07-04 7:06 ` Paolo Bonzini
2014-07-04 7:50 ` 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=53B562C0.6020606@redhat.com \
--to=eblake@redhat.com \
--cc=kwolf@redhat.com \
--cc=ming.lei@canonical.com \
--cc=pbonzini@redhat.com \
--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).