From: Pankaj Gupta <pagupta@redhat.com>
To: qemu-devel@nongnu.org
Cc: Pankaj Gupta <pagupta@redhat.com>,
jasowang@redhat.com, aliguori@amazon.com, stefanha@redhat.com,
mst@redhat.com
Subject: [Qemu-devel] [PATCH v2] net:Enable vhost with vhostforce, vhost options for guests without MSI-X support
Date: Fri, 5 Jun 2015 20:02:29 +0530 [thread overview]
Message-ID: <1433514749-19584-1-git-send-email-pagupta@redhat.com> (raw)
We use vhostforce to enable vhost even if Guests don't have MSI-X support
and we fall back to QEMU virtio-net. This patch will enable vhost unconditionally
whenever we have vhostforce='ON' or vhost='ON'.
Initially, I wanted to remove vhostforce completely as an additional argument.
But after discussing this in mailing list found that some programs are using vhostforce
and some vhost. So, we want to keep semantics of both the options.
Signed-off-by: Pankaj Gupta <pagupta@redhat.com>
---
net/tap.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/net/tap.c b/net/tap.c
index d1ca314..4618359 100644
--- a/net/tap.c
+++ b/net/tap.c
@@ -649,13 +649,13 @@ static void net_init_tap_one(const NetdevTapOptions *tap, NetClientState *peer,
}
}
- if (tap->has_vhost ? tap->vhost :
- vhostfdname || (tap->has_vhostforce && tap->vhostforce)) {
+ if ((tap->has_vhost ? tap->vhost :
+ vhostfdname) || tap->vhostforce) {
VhostNetOptions options;
options.backend_type = VHOST_BACKEND_TYPE_KERNEL;
options.net_backend = &s->nc;
- options.force = tap->has_vhostforce && tap->vhostforce;
+ options.force = true;
if (tap->has_vhostfd || tap->has_vhostfds) {
vhostfd = monitor_fd_param(cur_mon, vhostfdname, &err);
--
1.9.3
next reply other threads:[~2015-06-05 14:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-05 14:32 Pankaj Gupta [this message]
2015-06-08 6:06 ` [Qemu-devel] [PATCH v2] net:Enable vhost with vhostforce, vhost options for guests without MSI-X support Jason Wang
2015-06-11 11:49 ` Pankaj Gupta
2015-06-12 8:09 ` Jason Wang
2015-06-12 9:22 ` Pankaj Gupta
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=1433514749-19584-1-git-send-email-pagupta@redhat.com \
--to=pagupta@redhat.com \
--cc=aliguori@amazon.com \
--cc=jasowang@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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;
as well as URLs for NNTP newsgroup(s).