[dpdk-dev,V2] doc: fix vhost setup in tep-termination app guide
Commit Message
- Fix vhost setup flags
- Add minor edits to improve readability and consistency
---
v2: - revert file mode changes made erroneously in v1
Signed-off-by: Mark Kavanagh <mark.b.kavanagh@intel.com>
---
doc/guides/sample_app_ug/tep_termination.rst | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
Comments
2016-07-21 14:10, Mark Kavanagh:
> - Fix vhost setup flags
> - Add minor edits to improve readability and consistency
>
> Signed-off-by: Mark Kavanagh <mark.b.kavanagh@intel.com>
Acked-by: John McNamara <john.mcnamara@intel.com>
Applied, thanks
@@ -59,8 +59,8 @@ This allows network isolation, QOS, etc to be provided on a per client basis.
In a typical setup, the network overlay tunnel is terminated at the Virtual/Tunnel End Point (VEP/TEP).
The TEP is normally located at the physical host level ideally in the software switch.
Due to processing constraints and the inevitable bottleneck that the switch
-becomes the ability to offload overlay support features becomes an important requirement.
-Intel® XL710 10/40 G Ethernet network card provides hardware filtering
+becomes, the ability to offload overlay support features becomes an important requirement.
+Intel® XL710 10/40 Gigabit Ethernet network card provides hardware filtering
and offload capabilities to support overlay networks implementations such as MAC in UDP and MAC in GRE.
Sample Code Overview
@@ -131,14 +131,14 @@ Compiling the Sample Code
.. code-block:: console
- CONFIG_RTE_LIBRTE_VHOST=n
+ CONFIG_RTE_LIBRTE_VHOST=y
vhost user is turned on by default in the configure file config/common_linuxapp.
To enable vhost cuse, disable vhost user.
.. code-block:: console
- CONFIG_RTE_LIBRTE_VHOST_USER=y
+ CONFIG_RTE_LIBRTE_VHOST_USER=n
After vhost is enabled and the implementation is selected, build the vhost library.