kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: Gleb Natapov <gleb@minantech.com>, KVM <kvm@vger.kernel.org>,
	linux-s390 <linux-s390@vger.kernel.org>,
	Cornelia Huck <cornelia.huck@de.ibm.com>,
	Alexander Graf <agraf@suse.de>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	Jens Freimann <jfrei@linux.vnet.ibm.com>
Subject: Re: [PATCHv2] kvm/irqchip: Speed up KVM_SET_GSI_ROUTING
Date: Mon, 24 Feb 2014 13:02:59 +0100	[thread overview]
Message-ID: <530B34F3.5000602@redhat.com> (raw)
In-Reply-To: <1393243126-27376-1-git-send-email-borntraeger@de.ibm.com>

Il 24/02/2014 12:58, Christian Borntraeger ha scritto:
> When starting lots of dataplane devices the bootup takes very long on my
> s390 system(prototype irqfd code). With larger setups we are even able
> to trigger some timeouts in some userspace components.
> Turns out that the KVM_SET_GSI_ROUTING ioctl takes very
> long (strace claims up to 0.1 sec) when having multiple CPUs.
> This is caused by the  synchronize_rcu and the HZ=100 of s390.
> By changing the code to use a private srcu we can speed things up.
>
> This patch reduces the boot time till mounting root from 8 to 2
> seconds on my s390 guest with 100 disks.
>
> Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
>
> ---
> v1-v2: Fix missing hunk in kvm_irq_has_notifier. This was unnoticed on
>        s390, as our code did not use it.

In fact, there are other accesses to irq_routing elsewhere in virt/kvm 
which should be changed to irq_srcu (which in turn probably means that 
it's better to make the SRCU instance per-VM).

My fault, I should have delayed the patch to after the merge window 
instead of doing a shoddy review.  I'll test the complete patch myself 
since VFIO is probably the only thing that can cover it 100%, and s390 
doesn't do VFIO.

Paolo

      reply	other threads:[~2014-02-24 12:03 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-16  9:23 [PATCH] kvm/irqchip: Speed up KVM_SET_GSI_ROUTING Christian Borntraeger
2014-01-16 11:24 ` Paolo Bonzini
2014-01-16 12:44   ` [PATCHv2/RFC] " Christian Borntraeger
2014-01-16 12:59     ` Paolo Bonzini
2014-01-16 13:06       ` Christian Borntraeger
2014-01-16 13:07         ` Paolo Bonzini
2014-01-16 18:56           ` Michael S. Tsirkin
2014-01-17  8:29             ` Christian Borntraeger
2014-01-17  9:19               ` Paolo Bonzini
2014-02-19 22:23               ` Paolo Bonzini
2014-02-21  4:59                 ` Andrew Theurer
2014-01-16 18:55     ` Michael S. Tsirkin
2014-01-16 20:07       ` [PATCHv3] " Christian Borntraeger
2014-01-16 20:22         ` Michael S. Tsirkin
2014-01-17 14:03           ` Paolo Bonzini
2014-01-17 15:03             ` Christian Borntraeger
2014-01-17 15:26               ` Paolo Bonzini
2014-02-21 17:35     ` [PATCHv2/RFC] " Paolo Bonzini
2014-02-24 11:58       ` [PATCHv2] " Christian Borntraeger
2014-02-24 12:02         ` Paolo Bonzini [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=530B34F3.5000602@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=agraf@suse.de \
    --cc=borntraeger@de.ibm.com \
    --cc=cornelia.huck@de.ibm.com \
    --cc=gleb@minantech.com \
    --cc=jfrei@linux.vnet.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=mst@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).