From: Xuan Ding <xuan.ding@intel.com>
To: maxime.coquelin@redhat.com, zhihong.wang@intel.com,
xiaolong.ye@intel.com
Cc: dev@dpdk.org, Xuan Ding <xuan.ding@intel.com>
Subject: [dpdk-dev] [PATCH v2] doc: add note for vhost builtin example
Date: Wed, 25 Mar 2020 04:21:15 +0000 [thread overview]
Message-ID: <20200325042115.84685-1-xuan.ding@intel.com> (raw)
In-Reply-To: <20200325014054.79051-1-xuan.ding@intel.com>
Add memory pre-allocation note for vhost example when enabling
"builtin-net-driver".
Signed-off-by: Xuan Ding <xuan.ding@intel.com>
---
v2:
* Modified expression in doc to make it more accurate.
---
doc/guides/sample_app_ug/vhost.rst | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/doc/guides/sample_app_ug/vhost.rst b/doc/guides/sample_app_ug/vhost.rst
index a71ada654..b7ed4f8bd 100644
--- a/doc/guides/sample_app_ug/vhost.rst
+++ b/doc/guides/sample_app_ug/vhost.rst
@@ -201,3 +201,10 @@ Common Issues
QEMU vhost net device start will fail if protocol feature is not negotiated.
DPDK virtio-user pmd can be the replacement of QEMU.
+
+* Device start fails when enabling "builtin-net-driver" without memory
+ pre-allocation
+
+ The builtin example doesn't support dynamic memory allocation. When vhost
+ backend enables "builtin-net-driver", "--socket-mem" option should be
+ added at virtio-user pmd side as a startup item.
--
2.17.1
next prev parent reply other threads:[~2020-03-25 4:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-25 1:40 [dpdk-dev] [PATCH] " Xuan Ding
2020-03-25 4:21 ` Xuan Ding [this message]
2020-04-15 11:10 ` [dpdk-dev] [PATCH v2] " Maxime Coquelin
2020-04-17 17:13 ` Maxime Coquelin
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=20200325042115.84685-1-xuan.ding@intel.com \
--to=xuan.ding@intel.com \
--cc=dev@dpdk.org \
--cc=maxime.coquelin@redhat.com \
--cc=xiaolong.ye@intel.com \
--cc=zhihong.wang@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).