From: Joel Schopp <joel.schopp@amd.com>
To: "Shannon Zhao" <zhaoshenglong@huawei.com>,
"GAUGUEY Rémy 228890" <remy.gauguey@cea.fr>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "peter.maydell@linaro.org" <peter.maydell@linaro.org>,
"hangaohuai@huawei.com" <hangaohuai@huawei.com>,
"john.liuli@huawei.com" <john.liuli@huawei.com>,
"mst@redhat.com" <mst@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"n.nikolaev@virtualopensystems.com"
<n.nikolaev@virtualopensystems.com>,
"virtualization@lists.linux-foundation.org"
<virtualization@lists.linux-foundation.org>,
"peter.huangpeng@huawei.com" <peter.huangpeng@huawei.com>
Subject: Re: [Qemu-devel] [RFC PATCH] virtio-mmio: support for multiple irqs
Date: Wed, 5 Nov 2014 09:27:29 -0600 [thread overview]
Message-ID: <545A41E1.10303@amd.com> (raw)
In-Reply-To: <5459EA0E.8020309@huawei.com>
On 11/05/2014 03:12 AM, Shannon Zhao wrote:
> Hi Rémy,
>
> On 2014/11/5 16:26, GAUGUEY Rémy 228890 wrote:
>> Hi Shannon,
>>
>>> Type of backend bandwith(GBytes/sec)
>>> virtio-net 0.66
>>> vhost-net 1.49
>>> vhost-net with irqfd 2.01
>>>
>>> Test cmd: ./iperf -c 192.168.0.2 -P 1 -i 10 -p 5001 -f G -t 60
>> Impressive results !
>> Could you please detail your setup ? which platform are you using and which GbE controller ?
> Sorry for not telling the test scenario. This test scenario is from Host to Guest. It just
> compare the performance of different backends. I did this test on ARM64 platform.
>
> The setup was based on:
> 1)on host kvm-arm should support ioeventfd and irqfd
> The irqfd patch is from Eric "ARM: KVM: add irqfd support".
> http://www.spinics.net/lists/kvm-arm/msg11014.html
>
> The ioeventfd patch is reworked by me from Antonios.
> http://www.spinics.net/lists/kvm-arm/msg08413.html
>
> 2)qemu should enable ioeventfd support for virtio-mmio
> This patch is refer to Ying-Shiuan Pan and reworked for new qemu branch.
> https://lists.gnu.org/archive/html/qemu-devel/2014-11/msg00594.html
>
> 3)qemu should enable multiple irqs for virtio-mmio
> This patch isn't sent to qemu maillist as we want to check whether this is the right direction.
> If you want to test, I'll send it to you.
I'm not a maintainer so my opinion isn't worth a lot here, but this
seems like the right direction to me. I'd like to see the qemu patch
(do mention the dependency on the kernel patch) on the qemu-devel
mailing list. I think these numbers also support some of the prereqs
listed above that have gone through several iterations getting queued up
for 3.19.
next prev parent reply other threads:[~2014-11-05 15:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-04 9:35 Shannon Zhao
2014-11-05 7:59 ` Shannon Zhao
2014-11-05 8:26 ` GAUGUEY Rémy 228890
2014-11-05 9:12 ` Shannon Zhao
2014-11-05 15:27 ` Joel Schopp [this message]
2014-11-06 3:26 ` [Qemu-devel] " Shannon Zhao
2014-11-06 9:34 ` Michael S. Tsirkin
2014-11-06 9:54 ` Shannon Zhao
2014-11-06 11:09 ` Michael S. Tsirkin
2014-11-07 2:36 ` Shannon Zhao
2014-11-11 15:11 ` Pawel Moll
2014-11-12 8:32 ` Shannon Zhao
2014-11-12 18:33 ` Pawel Moll
2014-11-13 9:39 ` Shannon Zhao
2014-11-14 17:54 ` Pawel Moll
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=545A41E1.10303@amd.com \
--to=joel.schopp@amd.com \
--cc=hangaohuai@huawei.com \
--cc=john.liuli@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=n.nikolaev@virtualopensystems.com \
--cc=peter.huangpeng@huawei.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=remy.gauguey@cea.fr \
--cc=virtualization@lists.linux-foundation.org \
--cc=zhaoshenglong@huawei.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
Powered by JetHome