From: "Peter Lieven" <lieven-lists@dlhnet.de>
To: Dietmar Maurer <dietmar@proxmox.com>
Cc: Stefan Hajnoczi <stefanha@gmail.com>,
Peter Lieven <lieven-lists@dlhnet.de>,
Jan Kiszka <jan.kiszka@web.de>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] slow virtio network with vhost=on and multiple cores
Date: Thu, 8 Nov 2012 16:02:23 +0100 [thread overview]
Message-ID: <aef60421b7d2d0df5b3742e515e466a1.squirrel@ssl.dlhnet.de> (raw)
In-Reply-To: <24E144B8C0207547AD09C467A8259F75577EDCC2@lisa.maurer-it.com>
Dietmar Maurer wrote:
>> Meanwhile I quickly tried to reproduce but didn't succeed so far
>> (>10GBit
>> between host and guest with vhost=on and 2 guest cores).
>> However, I finally realized that we are talking about a pretty special
>> host
>> kernel which I don't have around. I guess this is better dealt with by
>> Red Hat
>> folks. Specifically, they should know what features that kernel exposes
>> and
>> what it lacks.
>
> You can also reproduce the bug with Ubuntu 12.04 on the host - it is not
> red-hat related.
Dietmar, how is the speed if you specify --machine pc,kernel_irqchip=off
as cmdline option to qemu-kvm-1.2.0?
Peter
next prev parent reply other threads:[~2012-11-08 15:02 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 [this message]
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
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=aef60421b7d2d0df5b3742e515e466a1.squirrel@ssl.dlhnet.de \
--to=lieven-lists@dlhnet.de \
--cc=dietmar@proxmox.com \
--cc=jan.kiszka@web.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).