From: Ying-Shiuan Pan <yingshiuan.pan@gmail.com>
To: qemu-devel@nongnu.org
Cc: wbarak@gmail.com, Ying-Shiuan Pan <yingshiuan.pan@gmail.com>,
yspan@itri.org.tw
Subject: [Qemu-devel] [PATCH 0/4] ioeventfd support for virtio-mmio
Date: Thu, 6 Feb 2014 01:03:35 +0800 [thread overview]
Message-ID: <1391619819-10525-1-git-send-email-yingshiuan.pan@gmail.com> (raw)
I added host/guest notifiers support for virtio-mmio, so that qemu can
enable vhost-net for kvm-arm. Sorry for that I cannot measure the performance
difference because I have only Exynos-5250 arndale boards which only provide
a 100 Mbps Ethernet. But in our previous work in kvm-arm (refer: Evaluation of
a Server-Grade Software-Only ARM Hypervisor), the vhost-net increased at least
30% in throughput comparing to virtio-net.
Ying-Shiuan Pan (4):
virtio-mmio: introduce set_host_notifier()
virtio-mmio: introduce set_guest_notifiers
virtio-mmio: start ioeventfd when status gets DRIVER_OK
virtio-mmio: add a new property for ioeventfd
hw/block/virtio-blk.c | 1 +
hw/net/virtio-net.c | 1 +
hw/virtio/virtio-mmio.c | 176 +++++++++++++++++++++++++++++++++++++++++++++
include/hw/virtio/virtio.h | 1 +
4 files changed, 179 insertions(+)
--
1.8.1.2
next reply other threads:[~2014-02-05 17:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-05 17:03 Ying-Shiuan Pan [this message]
2014-02-05 17:03 ` [Qemu-devel] [PATCH 1/4] virtio-mmio: introduce set_host_notifier() Ying-Shiuan Pan
2014-02-05 17:03 ` [Qemu-devel] [PATCH 2/4] virtio-mmio: introduce set_guest_notifiers Ying-Shiuan Pan
2014-02-05 17:03 ` [Qemu-devel] [PATCH 3/4] virtio-mmio: start ioeventfd when status gets DRIVER_OK Ying-Shiuan Pan
2014-02-05 17:03 ` [Qemu-devel] [PATCH 4/4] virtio-mmio: add a new property for ioeventfd Ying-Shiuan Pan
-- strict thread matches above, loose matches on Subject: below --
2014-11-04 12:47 [Qemu-devel] [PATCH 0/4] ioeventfd support for virtio-mmio Shannon Zhao
2014-11-05 9:33 ` Shannon Zhao
2015-01-22 7:47 ` Paolo Bonzini
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=1391619819-10525-1-git-send-email-yingshiuan.pan@gmail.com \
--to=yingshiuan.pan@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=wbarak@gmail.com \
--cc=yspan@itri.org.tw \
/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).