public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: Alex Williamson <alex.williamson@redhat.com>,
	kvm <kvm@vger.kernel.org>, "Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [RFT] IRQ sharing for assigned devices - method selection
Date: Sun, 09 Jan 2011 11:42:34 +0200	[thread overview]
Message-ID: <4D29830A.403@redhat.com> (raw)
In-Reply-To: <4D276377.2090000@web.de>

On 01/07/2011 09:03 PM, Jan Kiszka wrote:
> >>
> >>  So, if you have a good high-bandwidth test case at hand, I would
> >>  appreciate if you could give this a try and report your findings. Does
> >>  switching from exclusive to shared IRQ mode decrease the throughput or
> >>  increase the host load? Is there a difference to current kvm?
> >
> >  I think any sufficiently high bandwidth device will be using MSI and or
> >  NAPI, so I wouldn't expect we're going to see much change there.
>
> That's also why I'm no longer sure it's worth to worry about irq_disable
> vs. PCI disable. Anyone who cares about performance in a large
> pass-through scenario will try to use MSI-capable hardware anyway (or
> was so far unable to use tons of legacy IRQ driven devices due to IRQ
> conflicts).

PCI disable is probably only ridiculously slow with cf8/cfc config space 
access, and significantly faster (though still slow) with mmconfig.  
Needs to be taken into account as well.

-- 
error compiling committee.c: too many arguments to function


      reply	other threads:[~2011-01-09  9:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-07  9:33 [RFT] IRQ sharing for assigned devices - method selection Jan Kiszka
2011-01-07 18:57 ` Alex Williamson
2011-01-07 19:03   ` Jan Kiszka
2011-01-09  9:42     ` Avi Kivity [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=4D29830A.403@redhat.com \
    --to=avi@redhat.com \
    --cc=alex.williamson@redhat.com \
    --cc=jan.kiszka@web.de \
    --cc=kvm@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