From: Asias He <asias@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
qemu-devel@nongnu.org, kvm@vger.kernel.org,
Peter Maydell <peter.maydell@linaro.org>
Subject: Re: [Qemu-devel] [PATCH] kvm: do not flush after deleting gsi
Date: Thu, 13 Dec 2012 12:55:51 +0800 [thread overview]
Message-ID: <50C95FD7.9040205@redhat.com> (raw)
In-Reply-To: <20121212104821.GA6324@redhat.com>
Hello Michael,
On 12/12/2012 06:48 PM, Michael S. Tsirkin wrote:
> Deleting a GSI isn't necessary: it is enough
> to stop using it. Delay flush until an entry is used.
>
> Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
> ---
> kvm-all.c | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/kvm-all.c b/kvm-all.c
> index 3bc3347..fb3180d 100644
> --- a/kvm-all.c
> +++ b/kvm-all.c
> @@ -991,8 +991,6 @@ void kvm_irqchip_release_virq(KVMState *s, int virq)
> }
> }
> clear_gsi(s, virq);
> -
> - kvm_irqchip_commit_routes(s);
> }
>
> static unsigned int kvm_hash_msi(uint32_t data)
>
I tried this patch with vhost-blk with qemu-1.3.0
6d6c9f59ca1b1a76ade7ad868bef191818f58819.
Without the drop of msix_fire_vector_notifier in msix_handle_mask_update
hack
Before: ~20K IOPS
After: ~35K IOPS
With the drop of msix_fire_vector_notifier in
msix_handle_mask_update hack
Before: ~197K IOPS
After: ~197K IOPS
--
Asias
next prev parent reply other threads:[~2012-12-13 4:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-12 10:48 [Qemu-devel] [PATCH] kvm: do not flush after deleting gsi Michael S. Tsirkin
2012-12-12 11:39 ` Jan Kiszka
2012-12-13 4:55 ` Asias He [this message]
2012-12-13 15:34 ` Jan Kiszka
2012-12-14 1:00 ` Asias He
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=50C95FD7.9040205@redhat.com \
--to=asias@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=mst@redhat.com \
--cc=mtosatti@redhat.com \
--cc=peter.maydell@linaro.org \
--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).