qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Ying-Shiuan Pan <yingshiuan.pan@gmail.com>
To: Barak Wasserstrom <wbarak@gmail.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	QEMU Developers <qemu-devel@nongnu.org>,
	Pawel Moll <pawel.moll@arm.com>
Subject: Re: [Qemu-devel] Using virtio-net and vhost_net on an ARM machine using qemu-system-arm & KVM
Date: Mon, 13 Jan 2014 11:47:11 +0800	[thread overview]
Message-ID: <CAA1vHqKGU3KUHB4J=obAp7z2YmN1gcbgbfoK_04gda6eAijUgQ@mail.gmail.com> (raw)
In-Reply-To: <CAFEAcA-=vgrE7XFo76pmuKZ8Yawn5e5Od6UtWnJTgn6xCXaadw@mail.gmail.com>

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

Hi, Barak,

We've tried vhost-net in kvm-arm on arndale Exynos-5250 board (it requires
some patches in qemu and kvm, of course). It works (without irqfd support),
however, the performance does not increase much. The throughput (iperf) of
virtio-net and vhost-net are 93.5Mbps and 93.6Mbps respectively. I thought
the result are because both virtio-net and vhost-net almost reached the
limitation of 100Mbps Ethernet.

The good news is that we even ported vhost-net in our kvm-a9 hypervisor
(refer:
http://academic.odysci.com/article/1010113020064758/evaluation-of-a-server-grade-software-only-arm-hypervisor),
and the throughput of vhost-net on that platform (with 1Gbps Ethernet)
increased from 323Mbps to 435Mbps.

--
Ying-Shiuan Pan,
H Div., CCMA, ITRI, TW


----
Best Regards,
潘穎軒Ying-Shiuan Pan


2014/1/13 Peter Maydell <peter.maydell@linaro.org>

> On 12 January 2014 21:49, Barak Wasserstrom <wbarak@gmail.com> wrote:
> > Thanks - I got virtio-net-device running now, but performance is
> terrible.
> > When i look at the guest's ethernet interface features (ethtool -k eth0)
> i
> > see all offload features are disabled.
> > I'm using a virtual tap on the host (tap0 bridged to eth3).
> > On the tap i also see all offload features are disabled, while on br0 and
> > eth3 i see the expected offload features.
> > Can this explain the terrible performance i'm facing?
> > If so, how can this be changed?
> > If not, what else can cause such bad performance?
> > Do you know if vhost_net can be used on ARM Cortex A15 host/guest, even
> > though the guest doesn't support PCI & MSIX?
>
> I have no idea, I'm afraid. I don't have enough time available to
> investigate performance issues at the moment; if you find anything
> specific you can submit patches...
>
> thanks
> -- PMM
>
>

[-- Attachment #2: Type: text/html, Size: 2522 bytes --]

  reply	other threads:[~2014-01-13  3:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-09 12:25 [Qemu-devel] Using virtio-net and vhost_net on an ARM machine using qemu-system-arm & KVM Barak Wasserstrom
2014-01-12 21:15 ` Peter Maydell
2014-01-12 21:49   ` Barak Wasserstrom
2014-01-12 22:00     ` Peter Maydell
2014-01-13  3:47       ` Ying-Shiuan Pan [this message]
2014-01-13 11:24         ` Barak Wasserstrom
2014-01-14  3:37           ` Ying-Shiuan Pan
2014-01-14 11:11             ` Barak Wasserstrom
2014-01-15  2:42               ` Ying-Shiuan Pan
2014-01-16  7:29                 ` Barak Wasserstrom

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='CAA1vHqKGU3KUHB4J=obAp7z2YmN1gcbgbfoK_04gda6eAijUgQ@mail.gmail.com' \
    --to=yingshiuan.pan@gmail.com \
    --cc=pawel.moll@arm.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=wbarak@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).