From: Peter Lieven <pl@dlhnet.de>
To: Davide Guerri <d.guerri@unidata.it>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
Stefan Hajnoczi <stefanha@gmail.com>,
qemu-devel@nongnu.org, Alexandre DERUMIER <aderumier@odiso.com>,
Jan Kiszka <jan.kiszka@web.de>,
Peter Lieven <lieven-lists@dlhnet.de>,
Dietmar Maurer <dietmar@proxmox.com>
Subject: Re: [Qemu-devel] slow virtio network with vhost=on and multiple cores
Date: Fri, 15 Mar 2013 08:23:44 +0100 [thread overview]
Message-ID: <5142CC80.503@dlhnet.de> (raw)
In-Reply-To: <36D0FF56-686D-47DC-80FD-8DA6A5F48309@unidata.it>
On 15.03.2013 00:04, Davide Guerri wrote:
> Yes this is definitely an option :)
>
> Just for curiosity, what is the effect of "in-kernel irqchip"?
it emulates the irqchip in-kernel (in the KVM kernel module) which
avoids userspace exits to qemu. in your particular case I remember
that it made all IRQs deliverd to vcpu0 on. So I think this is a workaround
and not the real fix. I think Michael is right that it is a
client kernel bug. It would be good to find out what it is and ask
the 2.6.32 maintainers to include it. i further have seen that
with more recent kernels and inkernel-irqchip the irqs are delivered
to vcpu0 only again (without multiqueue).
> Is it possible to disable it on a "live" domain?
try it. i don't know. you definetely have to do a live migration for it,
but I have no clue if the VM will survice this.
Peter
>
> Cheers,
> Davide
>
>
> On 14/mar/2013, at 19:21, Peter Lieven <pl@dlhnet.de> wrote:
>
>>
>> Am 14.03.2013 um 19:15 schrieb Davide Guerri <d.guerri@unidata.it>:
>>
>>> Of course I can do some test but a kernel upgrade is not an option here :(
>>
>> disabling the in-kernel irqchip (default since 1.2.0) should also help, maybe this is an option.
>>
>> Peter
>>
>>
>
next prev parent reply other threads:[~2013-03-15 7:23 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-05 11:51 [Qemu-devel] slow virtio network with vhost=on and multiple cores Dietmar Maurer
2012-11-05 12:36 ` Stefan Hajnoczi
2012-11-05 15:01 ` Dietmar Maurer
2012-11-06 6:12 ` Dietmar Maurer
2012-11-06 7:46 ` Peter Lieven
2012-11-06 7:51 ` Dietmar Maurer
2012-11-06 9:01 ` Dietmar Maurer
2012-11-06 9:26 ` Jan Kiszka
2012-11-06 9:46 ` Dietmar Maurer
2012-11-06 10:12 ` Jan Kiszka
2012-11-06 11:24 ` Dietmar Maurer
2012-11-08 9:39 ` Jan Kiszka
2012-11-08 10:55 ` Peter Lieven
2012-11-08 12:03 ` Dietmar Maurer
2012-11-08 15:02 ` Peter Lieven
2012-11-09 5:55 ` Dietmar Maurer
2012-11-09 17:27 ` Peter Lieven
2012-11-09 17:51 ` Peter Lieven
2012-11-09 18:03 ` Peter Lieven
2012-11-13 11:44 ` Peter Lieven
2012-11-13 11:49 ` Peter Lieven
2012-11-13 16:22 ` Michael S. Tsirkin
2012-11-13 16:21 ` Peter Lieven
2012-11-13 16:26 ` Michael S. Tsirkin
2012-11-13 16:27 ` Peter Lieven
2012-11-13 16:59 ` Dietmar Maurer
2012-11-13 17:03 ` Michael S. Tsirkin
2012-11-13 16:33 ` Michael S. Tsirkin
2012-11-13 16:35 ` Peter Lieven
2012-11-13 16:46 ` Michael S. Tsirkin
2012-11-13 17:03 ` Dietmar Maurer
2012-11-13 17:07 ` Michael S. Tsirkin
2012-11-13 17:38 ` Dietmar Maurer
2012-11-15 18:26 ` Peter Lieven
2012-11-16 10:44 ` Dietmar Maurer
2012-11-16 11:00 ` Alexandre DERUMIER
2012-12-03 11:23 ` Peter Lieven
2012-12-09 18:38 ` Alexandre DERUMIER
2013-03-14 9:22 ` Davide Guerri
2013-03-14 10:43 ` Alexandre DERUMIER
2013-03-14 17:50 ` Michael S. Tsirkin
2013-03-14 18:15 ` Davide Guerri
2013-03-14 18:21 ` Peter Lieven
2013-03-14 23:04 ` Davide Guerri
2013-03-15 7:23 ` Peter Lieven [this message]
2013-03-17 9:08 ` Michael S. Tsirkin
2013-03-18 9:50 ` Alexandre DERUMIER
2013-03-18 9:53 ` Michael S. Tsirkin
2013-03-25 13:34 ` Peter Lieven
2012-11-19 13:49 ` Peter Lieven
2012-11-06 6:48 ` Dietmar Maurer
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=5142CC80.503@dlhnet.de \
--to=pl@dlhnet.de \
--cc=aderumier@odiso.com \
--cc=d.guerri@unidata.it \
--cc=dietmar@proxmox.com \
--cc=jan.kiszka@web.de \
--cc=lieven-lists@dlhnet.de \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.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).