qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: qemu-block@nongnu.org, pbonzini@redhat.com,
	qemu-devel@nongnu.org, stefanha@redhat.com
Subject: Re: [Qemu-devel] [Qemu-block] [PATCH] linux-aio: Cancel BH if not needed
Date: Fri, 17 Jun 2016 11:13:30 +0100	[thread overview]
Message-ID: <20160617101330.GE6994@stefanha-x1.localdomain> (raw)
In-Reply-To: <1465989402-18890-1-git-send-email-kwolf@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 2033 bytes --]

On Wed, Jun 15, 2016 at 01:16:42PM +0200, Kevin Wolf wrote:
> linux-aio uses a BH in order to make sure that the remaining completions
> are processed even in nested event loops of completion callbacks in
> order to avoid deadlocks.
> 
> There is no need, however, to have the BH overhead for the first call
> into qemu_laio_completion_bh() or after all pending completions have
> already been processed. Therefore, this patch calls directly into
> qemu_laio_completion_bh() in qemu_laio_completion_cb() and cancels
> the BH after qemu_laio_completion_bh() has processed all pending
> completions.
> 
> Signed-off-by: Kevin Wolf <kwolf@redhat.com>
> ---
>  block/linux-aio.c | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)

I ran 4 x iodepth=16 random 4KB read I/O benchmarks.  There might be an
improvement but it's within the error margin.  My benchmarking setup can
be noisy...

Anyway, this patch doesn't hurt performance.  Guest and host are RHEL 7.2.

$ ./analyze.py runs/
Name                                          IOPS   Error
linux-aio-bh-optimizations-ccb9dc1      12942616.0 ± 16.83%
linux-aio-bh-optimizations-ccb9dc1-2    13833110.4 ± 4.74%
linux-aio-bh-optimizations-off-23b0d9f  13303981.4 ± 2.21%

qemu-system-x86_64 -pidfile qemu.pid -daemonize \
                   -machine accel=kvm -cpu host \
		   -smp 4 -m 1024 \
		   -netdev user,id=netdev0,hostfwd=tcp::2222-:22 \
                   -object iothread,id=iothread0 \
		   -device virtio-net-pci,netdev=netdev0 \
		   -drive if=none,id=drive0,file=/var/lib/libvirt/images/test.img,format=raw,aio=native,cache=none \
                   -device virtio-blk-pci,drive=drive0 \
		   -drive if=none,id=drive1,file=/dev/nullb0,format=raw,aio=native,cache=none \
                   -device virtio-blk-pci,drive=drive1 \
		   -display none

$ cat fio.job
[global]
filename=/dev/vdb
ioengine=libaio
direct=1
runtime=60
ramp_time=5
gtod_reduce=1

[job1]
numjobs=4
iodepth=16
rw=randread
bs=4K

Stefan

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

  parent reply	other threads:[~2016-06-17 10:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-15 11:16 [Qemu-devel] [PATCH] linux-aio: Cancel BH if not needed Kevin Wolf
2016-06-15 12:39 ` Paolo Bonzini
2016-06-16 16:08 ` Stefan Hajnoczi
2016-06-17 10:13 ` Stefan Hajnoczi [this message]
2016-06-17 10:24   ` [Qemu-devel] [Qemu-block] " Kevin Wolf
2016-06-20 10:34     ` 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=20160617101330.GE6994@stefanha-x1.localdomain \
    --to=stefanha@gmail.com \
    --cc=kwolf@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-block@nongnu.org \
    --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).