From: Stefan Hajnoczi <stefanha@redhat.com>
To: qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Karl Rister <krister@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] iothread: enable AioContext polling by default
Date: Tue, 31 Jan 2017 17:09:44 +0000 [thread overview]
Message-ID: <20170131170944.GA25011@stefanha-x1.localdomain> (raw)
In-Reply-To: <20170126170119.27876-1-stefanha@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1058 bytes --]
On Thu, Jan 26, 2017 at 05:01:19PM +0000, Stefan Hajnoczi wrote:
> IOThread AioContexts are likely to consist only of event sources like
> virtqueue ioeventfds and LinuxAIO completion eventfds that are pollable
> from userspace (without system calls).
>
> We recently merged the AioContext polling feature but didn't enable it
> by default yet. I have gone back over the performance data on the
> mailing list and picked a default polling value that gave good results.
>
> Let's enable AioContext polling by default so users don't have another
> switch they need to set manually. If performance regressions are found
> we can still disable this for the QEMU 2.9 release.
>
> Cc: Paolo Bonzini <pbonzini@redhat.com>
> Cc: Christian Borntraeger <borntraeger@de.ibm.com>
> Cc: Karl Rister <krister@redhat.com>
> Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
> ---
> iothread.c | 14 ++++++++++++++
> 1 file changed, 14 insertions(+)
Thanks, applied to my block tree:
https://github.com/stefanha/qemu/commits/block
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
prev parent reply other threads:[~2017-01-31 17:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-26 17:01 [Qemu-devel] [PATCH] iothread: enable AioContext polling by default Stefan Hajnoczi
2017-01-27 16:07 ` Paolo Bonzini
2017-01-31 17:09 ` Stefan Hajnoczi [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=20170131170944.GA25011@stefanha-x1.localdomain \
--to=stefanha@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=krister@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).