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 1/2] coroutine: make pool size dynamic
Date: Thu, 03 Jul 2014 07:59:10 -0600 [thread overview]
Message-ID: <53B561AE.3050307@redhat.com> (raw)
In-Reply-To: <1404395521-11158-2-git-send-email-stefanha@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 805 bytes --]
On 07/03/2014 07:52 AM, Stefan Hajnoczi wrote:
> Allow coroutine users to adjust the pool size. For example, if the
> guest has multiple emulated disk drives we should keep around more
> coroutines.
>
> Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
> ---
> include/block/coroutine.h | 11 +++++++++++
> qemu-coroutine.c | 25 +++++++++++++++++++------
> 2 files changed, 30 insertions(+), 6 deletions(-)
>
> +
> +void qemu_coroutine_adjust_pool_size(int n)
> +{
> + qemu_mutex_lock(&pool_lock);
> +
> + pool_max_size += n;
Where do you check that this doesn't fall below a bare-minimum
acceptable level? Is it worth assert(pool_max_size >= 64)?
--
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 13:59 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 [this message]
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
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=53B561AE.3050307@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.