From: Flavio Leitner <fbl@redhat.com>
To: Jason Wang <jasowang@redhat.com>, "Michael S. Tsirkin" <mst@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] vhost-user breaks after 96a3d98.
Date: Fri, 30 Dec 2016 10:41:30 -0200 [thread overview]
Message-ID: <20161230104130.29ff671b@x240.lan> (raw)
Hi,
While I was testing vhost-user using OVS 2.5 and DPDK 2.2.0 in the
host and testpmd dpdk 2.2.0 in the guest, I found that the commit
below breaks the environment and no packets gets into the guest.
dpdk port --> OVS --> vhost-user --> guest --> testpmd
^--- drops here ^--- no packets here.
commit 96a3d98d2cdbd897ff5ab33427aa4cfb94077665
Author: Jason Wang <jasowang@redhat.com>
Date: Mon Aug 1 16:07:58 2016 +0800
vhost: don't set vring call if no vector
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.
[...]
Thanks,
--
Flavio
next reply other threads:[~2016-12-30 12:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-30 12:41 Flavio Leitner [this message]
2017-01-03 3:09 ` [Qemu-devel] vhost-user breaks after 96a3d98 Jason Wang
2017-01-03 10:28 ` Jason Wang
2017-01-03 16:27 ` Michael S. Tsirkin
2017-01-04 3:26 ` Jason Wang
2017-01-04 7:52 ` Jason Wang
2017-01-04 13:00 ` Flavio Leitner
2017-01-04 13:10 ` Michael S. Tsirkin
2017-01-03 17:33 ` Flavio Leitner
2017-01-03 22:13 ` Michael S. Tsirkin
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=20161230104130.29ff671b@x240.lan \
--to=fbl@redhat.com \
--cc=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).