From: Jason Wang <jasowang@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 5/6] virtio-pci: introduce pio notification capability for modern device
Date: Wed, 26 Aug 2015 13:29:40 +0800 [thread overview]
Message-ID: <55DD4EC4.3070908@redhat.com> (raw)
In-Reply-To: <20150825144732-mutt-send-email-mst@redhat.com>
On 08/25/2015 07:48 PM, Michael S. Tsirkin wrote:
> On Fri, Aug 21, 2015 at 05:05:49PM +0800, Jason Wang wrote:
>> > We used to use mmio for notification. This could be slow on some arch
>> > (e.g on x86 without EPT). So this patch introduces pio bar and a pio
>> > notification cap for modern device. This ability is enabled through
>> > property "modern-pio-notify" for virtio pci devices and was disabled
>> > by default. Management can enable when it thinks it was needed.
>> >
>> > Benchmarks shows almost no obvious difference with legacy device.
>> > Thanks Wenli Quan <wquan@redhat.com> for the benchmarking.
>> >
>> > Cc: Michael S. Tsirkin <mst@redhat.com>
>> > Signed-off-by: Jason Wang <jasowang@redhat.com>
> I don't really care much about non-EPT hosts, but if you propose
> a patch to optimize them, it should be accompanied by numbers
> showing the performance difference.
>
According to the test, PIO is a little bit faster than fast mmio in some
specific TCP_RR case:
modern device fast mmio vs modern device pio:
TCP_RR:
size/session/+transaction rate%/+cpu%/-+per cpu%/
64/1/[+1.5646%]/+5.6604%/-4.3415%/
64/25/+0.3003%/-0.4517%/+0.7486%/
...
256/1/[+1.0046%]/[-6.5238%]/[+7.0673%]/
So the improvement is almost as much as previous patch.
next prev parent reply other threads:[~2015-08-26 5:29 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-21 9:05 [Qemu-devel] [PATCH 0/6] virtio pci 1.0 optimizations and fixes Jason Wang
2015-08-21 9:05 ` [Qemu-devel] [PATCH 1/6] pc: introduce 2.5 machine type Jason Wang
2015-08-21 15:47 ` Eduardo Habkost
2015-08-24 5:45 ` Jason Wang
2015-08-21 9:05 ` [Qemu-devel] [PATCH 2/6] ppc: spapr: " Jason Wang
2015-08-22 0:10 ` David Gibson
2015-08-24 5:37 ` Jason Wang
2015-08-21 9:05 ` [Qemu-devel] [PATCH 3/6] virtio-pci: fix 1.0 virtqueue migration Jason Wang
2015-08-21 9:43 ` Cornelia Huck
2015-08-24 5:37 ` Jason Wang
2015-08-24 14:14 ` Cornelia Huck
2015-08-25 3:14 ` Jason Wang
2015-08-21 9:05 ` [Qemu-devel] [PATCH 4/6] virtio-pci: use wildcard mmio eventfd for 1.0 notification cap Jason Wang
2015-08-24 16:30 ` Greg Kurz
2015-08-25 3:21 ` Jason Wang
2015-08-21 9:05 ` [Qemu-devel] [PATCH 5/6] virtio-pci: introduce pio notification capability for modern device Jason Wang
2015-08-24 14:52 ` Greg Kurz
2015-08-24 16:29 ` Greg Kurz
2015-08-25 11:48 ` Michael S. Tsirkin
2015-08-26 5:29 ` Jason Wang [this message]
2015-08-21 9:05 ` [Qemu-devel] [PATCH 6/6] virtio-pci: unbreak queue_enable read Jason Wang
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=55DD4EC4.3070908@redhat.com \
--to=jasowang@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).