From: Junjie Chen <junjie.j.chen@intel.com>
To: yliu@fridaylinux.org, maxime.coquelin@redhat.com, jianfeng.tan@intel.com
Cc: dev@dpdk.org, Junjie Chen <junjie.j.chen@intel.com>
Subject: [dpdk-dev] [PATCH] doc: add driver limitation for vhost dequeue zero copy
Date: Sat, 24 Feb 2018 09:44:13 -0500 [thread overview]
Message-ID: <1519483453-12613-1-git-send-email-junjie.j.chen@intel.com> (raw)
In vhost-switch example, when binding nic to vfio-pci, dequeue zero
copy cannot work in VM2NIC mode due to no iommu dma mapping is setup
for guest memory currently.
Signed-off-by: Junjie Chen <junjie.j.chen@intel.com>
---
doc/guides/sample_app_ug/vhost.rst | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/doc/guides/sample_app_ug/vhost.rst b/doc/guides/sample_app_ug/vhost.rst
index a4bdc6a..1591a31 100644
--- a/doc/guides/sample_app_ug/vhost.rst
+++ b/doc/guides/sample_app_ug/vhost.rst
@@ -147,7 +147,10 @@ retries on an RX burst, it takes effect only when rx retry is enabled. The
default value is 15.
**--dequeue-zero-copy**
-Dequeue zero copy will be enabled when this option is given.
+Dequeue zero copy will be enabled when this option is given, it is worth to
+note that if NIC is binded to vfio-pci driver, dequeue zero copy cannot work
+at VM2NIC mode (vm2vm=0) due to currently we don't setup iommu dma mapping for
+guest memory.
**--vlan-strip 0|1**
VLAN strip option is removed, because different NICs have different behaviors
--
2.0.1
next reply other threads:[~2018-02-24 7:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-24 14:44 Junjie Chen [this message]
2018-02-26 4:44 ` Tan, Jianfeng
2018-03-13 9:12 ` Kovacevic, Marko
2018-03-13 9:18 ` Chen, Junjie J
2018-02-27 9:21 ` [dpdk-dev] [PATCH v2] " Junjie Chen
2018-03-06 8:57 ` Maxime Coquelin
2018-03-09 5:17 ` Chen, Junjie J
2018-03-09 10:07 ` [dpdk-dev] [PATCH v3] " Junjie Chen
2018-03-12 3:15 ` Tan, Jianfeng
2018-03-13 9:19 ` Chen, Junjie J
2018-03-14 16:24 ` [dpdk-dev] [PATCH v4] " Junjie Chen
2018-03-19 6:56 ` Tan, Jianfeng
2018-03-29 12:14 ` Maxime Coquelin
2018-04-11 14:34 ` 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=1519483453-12613-1-git-send-email-junjie.j.chen@intel.com \
--to=junjie.j.chen@intel.com \
--cc=dev@dpdk.org \
--cc=jianfeng.tan@intel.com \
--cc=maxime.coquelin@redhat.com \
--cc=yliu@fridaylinux.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).