From: Jason Wang <jasowang@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: cornelia.huck@de.ibm.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] vhost: don't set vring call if no vector
Date: Tue, 2 Aug 2016 10:37:14 +0800 [thread overview]
Message-ID: <0167ea42-35eb-d9e4-3054-ad9326914092@redhat.com> (raw)
In-Reply-To: <20160801162940-mutt-send-email-mst@kernel.org>
On 2016年08月01日 22:08, Michael S. Tsirkin wrote:
> On Mon, Aug 01, 2016 at 04:07:58PM +0800, Jason Wang wrote:
>> We used to set vring call fd unconditionally even if guest driver does
>> not use MSIX for this vritqueue at all. This will cause lots of
>> unnecessary userspace access and other checks for drivers does not use
>> interrupt at all (e.g virtio-net pmd). So check and clean vring call
>> fd if guest does not use any vector for this virtqueue at
>> all.
>>
>> Perf diffs (on rx) shows lots of cpus wasted on vhost_signal() were saved:
>>
>> #
>> 28.12% -27.82% [vhost] [k] vhost_signal
>> 14.44% -1.69% [kernel.vmlinux] [k] copy_user_generic_string
>> 7.05% +1.53% [kernel.vmlinux] [k] __free_page_frag
>> 6.51% +5.53% [vhost] [k] vhost_get_vq_desc
>> ...
>>
>> Pktgen tests shows 15.8% improvement on rx pps and 6.5% on tx pps.
>>
>> Before: RX 2.08Mpps TX 1.35Mpps
>> After: RX 2.41Mpps TX 1.44Mpps
>>
>> Signed-off-by: Jason Wang <jasowang@redhat.com>
>> ---
>> hw/virtio/vhost.c | 14 ++++++++++++++
>> 1 file changed, 14 insertions(+)
>>
>> diff --git a/hw/virtio/vhost.c b/hw/virtio/vhost.c
>> index 3d0c807..bd051ab 100644
>> --- a/hw/virtio/vhost.c
>> +++ b/hw/virtio/vhost.c
>> @@ -822,6 +822,9 @@ static int vhost_virtqueue_start(struct vhost_dev *dev,
>> struct vhost_virtqueue *vq,
>> unsigned idx)
>> {
>> + BusState *qbus = BUS(qdev_get_parent_bus(DEVICE(vdev)));
>> + VirtioBusState *vbus = VIRTIO_BUS(qbus);
>> + VirtioBusClass *k = VIRTIO_BUS_GET_CLASS(vbus);
>> hwaddr s, l, a;
>> int r;
>> int vhost_vq_index = dev->vhost_ops->vhost_get_vq_index(dev, idx);
>> @@ -912,8 +915,19 @@ static int vhost_virtqueue_start(struct vhost_dev *dev,
>> vhost_virtqueue_mask(dev, vdev, idx, false);
>> }
>>
>> + if (k->query_guest_notifiers &&
>> + k->query_guest_notifiers(qbus->parent) &&
>> + virtio_queue_vector(vdev, idx) == VIRTIO_NO_VECTOR) {
>> + file.fd = -1;
>> + r = dev->vhost_ops->vhost_set_vring_call(dev, &file);
>> + if (r) {
>> + goto fail_vector;
>> + }
>> + }
>> +
> It's rather asymmetrical though. Wouldn't a better place
> be in vhost_virtqueue_mask?
Looks not, since it will be only called when
- backend does not support interrupt masking (vhost-user), the patch
should work for vhost-kernel too
- mask or unmask an vector but the patch only work for a virtqueue of
VIRTIO_NO_VECTOR
>
>
>> return 0;
>>
>> +fail_vector:
>> fail_kick:
>> fail_alloc:
>> cpu_physical_memory_unmap(vq->ring, virtio_queue_get_ring_size(vdev, idx),
>> --
>> 2.7.4
next prev parent reply other threads:[~2016-08-02 2:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-01 8:07 [Qemu-devel] [PATCH] vhost: don't set vring call if no vector Jason Wang
2016-08-01 14:08 ` Michael S. Tsirkin
2016-08-02 2:37 ` Jason Wang [this message]
2016-08-01 18:00 ` Cornelia Huck
2016-08-02 2:39 ` Jason Wang
2016-08-02 6:37 ` Cornelia Huck
2016-08-03 1:48 ` 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=0167ea42-35eb-d9e4-3054-ad9326914092@redhat.com \
--to=jasowang@redhat.com \
--cc=cornelia.huck@de.ibm.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).