From: Gerd Hoffmann <kraxel@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH 2/2] virtio: enable msi-x for console+balloon
Date: Mon, 07 Dec 2009 11:32:36 +0100 [thread overview]
Message-ID: <4B1CD9C4.4020509@redhat.com> (raw)
In-Reply-To: <20091207093716.GA31370@redhat.com>
On 12/07/09 10:37, Michael S. Tsirkin wrote:
>
> Sorry, I missed this the first time this was posted, and I see this in
> staging now. Gerd, could you please explain the motivation for this
> patch?
>
> I assumed console/baloon interrupts are not performance critical, so
> would we not be better off using a shared interrupt for these,
> reserving MSI vectors for where performance matters?
The motivation was to move them away from the ioapic, to reduce irq
sharing of *other* devices which are connected to the ioapic too (i.e.
usb, e1000, lsi, ...)
I'm aware that these are not performance-critical. I've even tried to
use 'vectors=1' because of that. I expected that would make them use
MSI-X, but a single IRQ line only. Didn't work though. Intentional?
cheers,
Gerd
next prev parent reply other threads:[~2009-12-07 10:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-25 8:16 [Qemu-devel] [PATCH 1/2] pc: add machine type for 0.12 Gerd Hoffmann
2009-11-25 8:16 ` [Qemu-devel] [PATCH 2/2] virtio: enable msi-x for console+balloon Gerd Hoffmann
2009-12-07 9:37 ` [Qemu-devel] " Michael S. Tsirkin
2009-12-07 10:32 ` Gerd Hoffmann [this message]
2009-12-07 10:59 ` Michael S. Tsirkin
2009-12-07 11:24 ` Gerd Hoffmann
2009-12-07 13:03 ` Michael S. Tsirkin
2009-12-07 13:16 ` Gerd Hoffmann
2009-12-07 14:13 ` Michael S. Tsirkin
2009-12-07 14:30 ` Gerd Hoffmann
2009-12-07 14:43 ` Michael S. Tsirkin
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=4B1CD9C4.4020509@redhat.com \
--to=kraxel@redhat.com \
--cc=mst@redhat.com \
--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).