DPDK patches and discussions
 help / color / mirror / Atom feed
From: Marvin Liu <yong.liu@intel.com>
To: tiwei.bie@intel.com, dev@dpdk.org
Cc: Marvin Liu <yong.liu@intel.com>
Subject: [dpdk-dev] [PATCH] doc: add note for builtin-net-driver option
Date: Thu, 26 Jul 2018 01:12:24 +0800	[thread overview]
Message-ID: <20180725171224.21113-1-yong.liu@intel.com> (raw)

If builtin-net-driver option is enabled, simple vhost device will not
enable protocol feature bit. QEMU vhost net device startup will be
failed without protocol feature. Then QEMU process will be aborted when
reloading virtio net driver due to previous failure.

Signed-off-by: Marvin Liu <yong.liu@intel.com>

diff --git a/doc/guides/sample_app_ug/vhost.rst b/doc/guides/sample_app_ug/vhost.rst
index 9112e7897..01adae408 100644
--- a/doc/guides/sample_app_ug/vhost.rst
+++ b/doc/guides/sample_app_ug/vhost.rst
@@ -158,6 +158,10 @@ when disabling VLAN strip. Such feature, which heavily depends on hardware,
 should be removed from this example to reduce confusion. Now, VLAN strip is
 enabled and cannot be disabled.
 
+**--builtin-net-driver**
+The builtin-net-driver option enabled very simple enqueue and dequeue function.
+This option is disabled by default.
+
 Common Issues
 -------------
 
@@ -192,3 +196,10 @@ Common Issues
   according to the NIC's property. ::
 
       make EXTRA_CFLAGS="-DMAX_QUEUES=320"
+
+* QEMU abort when builtin-net-driver option enabled
+
+  QEMU vhost net device startup will be failed without
+  VHOST_USER_F_PROTOCOL_FEATURES feature bit. Thus will cause QEMU process
+  abort when reloading virtio driver. DPDK vhost-user can be the replacement
+  of QEMU.
-- 
2.17.0

             reply	other threads:[~2018-07-25  9:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-25 17:12 Marvin Liu [this message]
2018-07-26 14:27 ` [dpdk-dev] [PATCH v2] " Marvin Liu
2018-07-31  7:27   ` Tiwei Bie
2018-07-31 16:00   ` [dpdk-dev] [PATCH v3] " Marvin Liu
2018-08-07 13:52     ` Mcnamara, John
2018-08-09 19:21       ` Thomas Monjalon

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=20180725171224.21113-1-yong.liu@intel.com \
    --to=yong.liu@intel.com \
    --cc=dev@dpdk.org \
    --cc=tiwei.bie@intel.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).