qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>, qemu-devel@nongnu.org
Cc: Christian Borntraeger <borntraeger@de.ibm.com>,
	Karl Rister <krister@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] iothread: enable AioContext polling by default
Date: Fri, 27 Jan 2017 17:07:08 +0100	[thread overview]
Message-ID: <5f274867-7189-5bcd-d64b-f5ff31b0d54c@redhat.com> (raw)
In-Reply-To: <20170126170119.27876-1-stefanha@redhat.com>



On 26/01/2017 18:01, 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(+)
> 
> diff --git a/iothread.c b/iothread.c
> index 7bedde8..257b01d 100644
> --- a/iothread.c
> +++ b/iothread.c
> @@ -30,6 +30,12 @@ typedef ObjectClass IOThreadClass;
>  #define IOTHREAD_CLASS(klass) \
>     OBJECT_CLASS_CHECK(IOThreadClass, klass, TYPE_IOTHREAD)
>  
> +/* Benchmark results from 2016 on NVMe SSD drives show max polling times around
> + * 16-32 microseconds yield IOPS improvements for both iodepth=1 and iodepth=32
> + * workloads.
> + */
> +#define IOTHREAD_POLL_MAX_NS_DEFAULT 32768ULL
> +
>  static __thread IOThread *my_iothread;
>  
>  AioContext *qemu_get_current_aio_context(void)
> @@ -71,6 +77,13 @@ static int iothread_stop(Object *object, void *opaque)
>      return 0;
>  }
>  
> +static void iothread_instance_init(Object *obj)
> +{
> +    IOThread *iothread = IOTHREAD(obj);
> +
> +    iothread->poll_max_ns = IOTHREAD_POLL_MAX_NS_DEFAULT;
> +}
> +
>  static void iothread_instance_finalize(Object *obj)
>  {
>      IOThread *iothread = IOTHREAD(obj);
> @@ -215,6 +228,7 @@ static const TypeInfo iothread_info = {
>      .parent = TYPE_OBJECT,
>      .class_init = iothread_class_init,
>      .instance_size = sizeof(IOThread),
> +    .instance_init = iothread_instance_init,
>      .instance_finalize = iothread_instance_finalize,
>      .interfaces = (InterfaceInfo[]) {
>          {TYPE_USER_CREATABLE},
> 

ACK

Paolo

  reply	other threads:[~2017-01-27 16:07 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 [this message]
2017-01-31 17:09 ` 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=5f274867-7189-5bcd-d64b-f5ff31b0d54c@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=borntraeger@de.ibm.com \
    --cc=krister@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).