From: Paolo Bonzini <pbonzini@redhat.com>
To: Ming Lei <ming.lei@canonical.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
Stefan Hajnoczi <stefanha@gmail.com>,
qemu-devel <qemu-devel@nongnu.org>,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH for-2.1?!?] AioContext: speed up aio_notify
Date: Fri, 04 Jul 2014 09:27:39 +0200 [thread overview]
Message-ID: <53B6576B.7040304@redhat.com> (raw)
In-Reply-To: <CACVXFVN9VDrnopkM2q=Vsuk6_ES6-3_SHswSv5L+7_ToopetYA@mail.gmail.com>
Il 04/07/2014 09:23, Ming Lei ha scritto:
> I think it is good and better to go to 2.1, and it should save lots of
> write syscall.
>
> Also should regression be caused, the per thread trick may be
> resorted to, which should be simple.
If we have the "right" solution (which we do, unlike the plug/unplug
case), and the benefit is there but limited, I don't see a reason to
rush another patch in 2.1.
Some reasonable level of performance degradation or increased host CPU
utilization was expected in 2.1; of course 40% is not reasonable.
> With multi virtqueue's coming for virtio-blk, it should save more, and I
> also plan to use the improved qemu bh to help merge requests from
> multi queue, without introducing extra notifier.
But virtio-blk multiqueue is 2.2 material, and so is coalescing of irqfd
writes. I think Kevin or Stefan should queue this patch (with the
smp_mb optimization, IMHO) for block-next.
Paolo
next prev parent reply other threads:[~2014-07-04 7:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-03 16:59 [Qemu-devel] [PATCH for-2.1?!?] AioContext: speed up aio_notify Paolo Bonzini
2014-07-03 18:17 ` Stefan Hajnoczi
2014-07-04 6:51 ` Paolo Bonzini
2014-07-04 7:23 ` Ming Lei
2014-07-04 7:27 ` Paolo Bonzini [this message]
2014-07-04 10:26 ` Kevin Wolf
2014-07-04 10:40 ` Paolo Bonzini
2014-07-07 8:28 ` 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=53B6576B.7040304@redhat.com \
--to=pbonzini@redhat.com \
--cc=kwolf@redhat.com \
--cc=ming.lei@canonical.com \
--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).