From: Paolo Bonzini <pbonzini@redhat.com>
To: Ming Lei <ming.lei@canonical.com>
Cc: Kevin Wolf <kwolf@redhat.com>, qemu-devel <qemu-devel@nongnu.org>,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 0/2] coroutine: dynamically scale pool size
Date: Fri, 04 Jul 2014 09:06:56 +0200 [thread overview]
Message-ID: <53B65290.8070207@redhat.com> (raw)
In-Reply-To: <CACVXFVNMvyzE-=uBYKnevfbXnJe1pfWj5GGBnVVtwbzySaCJQA@mail.gmail.com>
Il 04/07/2014 09:02, Ming Lei ha scritto:
>> > So the excessive writes (to eventfd and irqfd) are not a problem? That'd be
>> > a relief. :)
> I mean it is in a level, but your aio_notify() patch still can improve virtioblk
> dataplane performance some, in my test, with 5~10K IOPS improvement,
> which should belong to same level, because my test is a bit coarse, :-)
>
> IMO not only virtioblk can benefit from your patch, others can benefit too.
Definitely, but it's not the kind of patch I enjoy including 3 weeks
from release. I have already broken enough eggs during the 2.1
development period. :)
Paolo
next prev parent reply other threads:[~2014-07-04 7:07 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
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 [this message]
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=53B65290.8070207@redhat.com \
--to=pbonzini@redhat.com \
--cc=kwolf@redhat.com \
--cc=ming.lei@canonical.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.