From: Li Liu <john.liuli@huawei.com>
To: Nikolay Nikolaev <n.nikolaev@virtualopensystems.com>
Cc: <kvmarm@lists.cs.columbia.edu>, <kvm@vger.kernel.org>,
qemu-devel <qemu-devel@nongnu.org>,
VirtualOpenSystems Technical Team <tech@virtualopensystems.com>
Subject: Re: The status about vhost-net on kvm-arm?
Date: Wed, 13 Aug 2014 10:23:39 +0800 [thread overview]
Message-ID: <53EACC2B.1090005@huawei.com> (raw)
In-Reply-To: <CADDJ2=Ovmrg-umksm0aEmyT0kBqruEq-iHpfbKSEg10zA-VEgA@mail.gmail.com>
On 2014/8/12 23:47, Nikolay Nikolaev wrote:
> Hello,
>
>
> On Tue, Aug 12, 2014 at 5:41 AM, Li Liu <john.liuli@huawei.com> wrote:
>>
>> Hi all,
>>
>> Is anyone there can tell the current status of vhost-net on kvm-arm?
>>
>> Half a year has passed from Isa Ansharullah asked this question:
>> http://www.spinics.net/lists/kvm-arm/msg08152.html
>>
>> I have found two patches which have provided the kvm-arm support of
>> eventfd and irqfd:
>>
>> 1) [RFC PATCH 0/4] ARM: KVM: Enable the ioeventfd capability of KVM on ARM
>> http://lists.gnu.org/archive/html/qemu-devel/2014-01/msg01770.html
>>
>> 2) [RFC,v3] ARM: KVM: add irqfd and irq routing support
>> https://patches.linaro.org/32261/
>>
>> And there's a rough patch for qemu to support eventfd from Ying-Shiuan Pan:
>>
>> [Qemu-devel] [PATCH 0/4] ioeventfd support for virtio-mmio
>> https://lists.gnu.org/archive/html/qemu-devel/2014-02/msg00715.html
>>
>> But there no any comments of this patch. And I can found nothing about qemu
>> to support irqfd. Do I lost the track?
>>
>> If nobody try to fix it. We have a plan to complete it about virtio-mmio
>> supporing irqfd and multiqueue.
>>
>>
>
> 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.
>
Yeah, we have roughly tested vhost-net without irqfd and get the same
result. And now try to see what will happen with 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).
>
>>
>>
>>
>>
>>
>> _______________________________________________
>> kvmarm mailing list
>> kvmarm@lists.cs.columbia.edu
>> https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
>
>
> regards,
> Nikolay Nikolaev
> Virtual Open Systems
>
> .
>
WARNING: multiple messages have this Message-ID (diff)
From: Li Liu <john.liuli@huawei.com>
To: 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: Wed, 13 Aug 2014 10:23:39 +0800 [thread overview]
Message-ID: <53EACC2B.1090005@huawei.com> (raw)
In-Reply-To: <CADDJ2=Ovmrg-umksm0aEmyT0kBqruEq-iHpfbKSEg10zA-VEgA@mail.gmail.com>
On 2014/8/12 23:47, Nikolay Nikolaev wrote:
> Hello,
>
>
> On Tue, Aug 12, 2014 at 5:41 AM, Li Liu <john.liuli@huawei.com> wrote:
>>
>> Hi all,
>>
>> Is anyone there can tell the current status of vhost-net on kvm-arm?
>>
>> Half a year has passed from Isa Ansharullah asked this question:
>> http://www.spinics.net/lists/kvm-arm/msg08152.html
>>
>> I have found two patches which have provided the kvm-arm support of
>> eventfd and irqfd:
>>
>> 1) [RFC PATCH 0/4] ARM: KVM: Enable the ioeventfd capability of KVM on ARM
>> http://lists.gnu.org/archive/html/qemu-devel/2014-01/msg01770.html
>>
>> 2) [RFC,v3] ARM: KVM: add irqfd and irq routing support
>> https://patches.linaro.org/32261/
>>
>> And there's a rough patch for qemu to support eventfd from Ying-Shiuan Pan:
>>
>> [Qemu-devel] [PATCH 0/4] ioeventfd support for virtio-mmio
>> https://lists.gnu.org/archive/html/qemu-devel/2014-02/msg00715.html
>>
>> But there no any comments of this patch. And I can found nothing about qemu
>> to support irqfd. Do I lost the track?
>>
>> If nobody try to fix it. We have a plan to complete it about virtio-mmio
>> supporing irqfd and multiqueue.
>>
>>
>
> 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.
>
Yeah, we have roughly tested vhost-net without irqfd and get the same
result. And now try to see what will happen with 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).
>
>>
>>
>>
>>
>>
>> _______________________________________________
>> kvmarm mailing list
>> kvmarm@lists.cs.columbia.edu
>> https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
>
>
> regards,
> Nikolay Nikolaev
> Virtual Open Systems
>
> .
>
next prev parent reply other threads:[~2014-08-13 2:24 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-12 2:41 The status about vhost-net on kvm-arm? Li Liu
2014-08-12 2:41 ` [Qemu-devel] " Li Liu
2014-08-12 7:29 ` Eric Auger
2014-08-12 7:29 ` [Qemu-devel] " Eric Auger
2014-08-13 2:11 ` Li Liu
2014-08-13 2:11 ` [Qemu-devel] " Li Liu
2014-08-12 15:47 ` Nikolay Nikolaev
2014-08-12 15:47 ` [Qemu-devel] " Nikolay Nikolaev
2014-08-13 2:23 ` Li Liu [this message]
2014-08-13 2:23 ` Li Liu
2014-08-13 2:31 ` Ying-Shiuan Pan
2014-08-13 2:31 ` [Qemu-devel] " Ying-Shiuan Pan
2014-08-13 9:10 ` Nikolay Nikolaev
2014-08-13 9:10 ` [Qemu-devel] " Nikolay Nikolaev
2014-08-13 11:07 ` Li Liu
2014-08-13 11:07 ` [Qemu-devel] " Li Liu
2014-08-13 11:25 ` Nikolay Nikolaev
2014-08-13 11:25 ` [Qemu-devel] " Nikolay Nikolaev
2014-08-14 3:50 ` Li Liu
2014-08-14 3:50 ` [Qemu-devel] " Li Liu
2014-08-14 15:58 ` Joel Schopp
2014-08-14 15:58 ` Joel Schopp
2014-08-15 3:04 ` Li Liu
2014-08-15 3:04 ` Li Liu
2014-08-15 7:24 ` Yingshiuan Pan
2014-08-15 7:24 ` [Qemu-devel] " Yingshiuan Pan
2014-10-15 14:39 ` GAUGUEY Rémy 228890
2014-10-15 14:39 ` [Qemu-devel] " GAUGUEY Rémy 228890
2014-10-17 12:26 ` Li Liu
2014-10-17 12:49 ` GAUGUEY Rémy 228890
2014-10-17 12:49 ` GAUGUEY Rémy 228890
2014-10-23 12:16 ` Li Liu
2014-10-23 12:16 ` [Qemu-devel] " Li Liu
[not found] ` <43311_1413383979_543E872B_43311_6388_1_022C7612790E20489F80A6F0D54B849F3B25B51A@EXDAG0-B3.intra.cea.fr>
2014-10-16 7:22 ` GAUGUEY Rémy 228890
2014-11-05 8:33 ` Shannon Zhao
2014-11-05 8:33 ` [Qemu-devel] " 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=53EACC2B.1090005@huawei.com \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.