All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@web.de>
To: kvm <kvm@vger.kernel.org>
Cc: Alex Williamson <alex.williamson@redhat.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	Avi Kivity <avi@redhat.com>
Subject: [RFT] IRQ sharing for assigned devices - method selection
Date: Fri, 07 Jan 2011 10:33:12 +0100	[thread overview]
Message-ID: <4D26DDD8.5040707@web.de> (raw)

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

Hi,

to finally select the approach for adding overdue IRQ sharing support
for PCI pass-through, I hacked up two versions based on Thomas' patches
and his suggestion to use a timeout-based mode transition:

    git://git.kiszka.org/linux-kvm.git queues/dev-assign.notify
    git://git.kiszka.org/linux-kvm.git queues/dev-assign.timeout

    git://git.kiszka.org/qemu-kvm.git queues/dev-assign

Both approaches work, but I'm either lacking a sufficiently stressing
test environment to tickle out a relevant delta, even between masking at
irqchip vs. PCI config space level - or there is none... Yes, there are
differences at micro level but they do not manifest in measurable (ie.
above the noise level) load increase or throughput/latency decrease in
my limited tests here. I that actually turns out to be true, I would
happily bury all this dynamic mode switching again.

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?

Thanks in advance,
Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 259 bytes --]

             reply	other threads:[~2011-01-07  9:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-07  9:33 Jan Kiszka [this message]
2011-01-07 18:57 ` [RFT] IRQ sharing for assigned devices - method selection Alex Williamson
2011-01-07 19:03   ` Jan Kiszka
2011-01-09  9:42     ` Avi Kivity

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=4D26DDD8.5040707@web.de \
    --to=jan.kiszka@web.de \
    --cc=alex.williamson@redhat.com \
    --cc=avi@redhat.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.