From: Joel Schopp <joel.schopp@amd.com>
To: Li Liu <john.liuli@huawei.com>,
Nikolay Nikolaev <n.nikolaev@virtualopensystems.com>
Cc: VirtualOpenSystems Technical Team <tech@virtualopensystems.com>,
kvmarm@lists.cs.columbia.edu, kvm@vger.kernel.org,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] The status about vhost-net on kvm-arm?
Date: Thu, 14 Aug 2014 10:58:26 -0500 [thread overview]
Message-ID: <53ECDCA2.5010808@amd.com> (raw)
In-Reply-To: <53EC31FF.4060903@huawei.com>
>>>> we at Virtual Open Systems did some work and tested vhost-net on ARM
>>>> back in March.
>>>> The setup was based on:
>>>> - host kernel with our ioeventfd patches:
>>>> http://www.spinics.net/lists/kvm-arm/msg08413.html
>>>>
>>>> - qemu with the aforementioned patches from Ying-Shiuan Pan
>>>> https://lists.gnu.org/archive/html/qemu-devel/2014-02/msg00715.html
>>>>
>>>> The testbed was ARM Chromebook with Exynos 5250, using a 1Gbps USB3
>>>> Ethernet adapter connected to a 1Gbps switch. I can't find the actual
>>>> numbers but I remember that with multiple streams the gain was clearly
>>>> seen. Note that it used the minimum required ioventfd implementation
>>>> and not irqfd.
>>>>
>>>> I guess it is feasible to think that it all can be put together and
>>>> rebased + the recent irqfd work. One can achiev even better
>>>> performance (because of the irqfd).
>>>>
>>> Managed to replicate the setup with the old versions e used in March:
>>>
>>> Single stream from another machine to chromebook with 1Gbps USB3
>>> Ethernet adapter.
>>> iperf -c <address> -P 1 -i 1 -p 5001 -f k -t 10
>>> to HOST: 858316 Kbits/sec
>>> to GUEST: 761563 Kbits/sec
>> to GUEST vhost=off: 508150 Kbits/sec
>>> 10 parallel streams
>>> iperf -c <address> -P 10 -i 1 -p 5001 -f k -t 10
>>> to HOST: 842420 Kbits/sec
>>> to GUEST: 625144 Kbits/sec
>> to GUEST vhost=off: 425276 Kbits/sec
> I have tested the same cases on a Hisilicon board (Cortex-A15@1G)
> with Integrated 1Gbps Ethernet adapter.
>
> iperf -c <address> -P 1 -i 1 -p 5001 -f M -t 10
> to HOST: 906 Mbits/sec
> to GUEST: 562 Mbits/sec
> to GUEST vhost=off: 340 Mbits/sec
>
> 10 parallel streams, the performance gets <10% plus:
> iperf -c <address> -P 10 -i 1 -p 5001 -f M -t 10
> to HOST: 923 Mbits/sec
> to GUEST: 592 Mbits/sec
> to GUEST vhost=off: 364 Mbits/sec
>
> I't easy to see vhost-net brings great performance improvements,
> almost 50%+.
That's pretty impressive for not even having irqfd. I guess we should
renew some effort to get these patches merged upstream.
next prev parent reply other threads:[~2014-08-14 15:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-12 2:41 [Qemu-devel] The status about vhost-net on kvm-arm? Li Liu
2014-08-12 7:29 ` Eric Auger
2014-08-13 2:11 ` Li Liu
2014-08-12 15:47 ` Nikolay Nikolaev
2014-08-13 2:23 ` Li Liu
2014-08-13 2:31 ` Ying-Shiuan Pan
2014-08-13 9:10 ` Nikolay Nikolaev
2014-08-13 11:07 ` Li Liu
2014-08-13 11:25 ` Nikolay Nikolaev
2014-08-14 3:50 ` Li Liu
2014-08-14 15:58 ` Joel Schopp [this message]
2014-08-15 3:04 ` Li Liu
2014-08-15 7:24 ` Yingshiuan Pan
2014-10-15 14:39 ` GAUGUEY Rémy 228890
2014-10-17 12:26 ` Li Liu
2014-10-17 12:49 ` GAUGUEY Rémy 228890
2014-10-23 12:16 ` Li Liu
2014-11-05 8:33 ` Shannon Zhao
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=53ECDCA2.5010808@amd.com \
--to=joel.schopp@amd.com \
--cc=john.liuli@huawei.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=n.nikolaev@virtualopensystems.com \
--cc=qemu-devel@nongnu.org \
--cc=tech@virtualopensystems.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).