From: "Tan, Jianfeng" <jianfeng.tan@intel.com>
To: "Kavanagh, Mark B" <mark.b.kavanagh@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] doc: fix vhost setup in tep-termination app guide
Date: Wed, 20 Jul 2016 01:49:03 +0000 [thread overview]
Message-ID: <ED26CBA2FAD1BF48A8719AEF02201E3610621F9F@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <1468942334-239956-1-git-send-email-mark.b.kavanagh@intel.com>
Hi Mark,
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Mark Kavanagh
> Sent: Tuesday, July 19, 2016 11:32 PM
> To: dev@dpdk.org
> Subject: [dpdk-dev] [PATCH] doc: fix vhost setup in tep-termination app
> guide
>
> - Fix vhost setup flags
> - Add minor edits to improve readability and consistency
>
> 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(-)
> mode change 100644 => 100755
> doc/guides/sample_app_ug/tep_termination.rst
>
> diff --git a/doc/guides/sample_app_ug/tep_termination.rst
> b/doc/guides/sample_app_ug/tep_termination.rst
> old mode 100644
> new mode 100755
> index 2d86a03..c3d1e97
> --- a/doc/guides/sample_app_ug/tep_termination.rst
> +++ b/doc/guides/sample_app_ug/tep_termination.rst
> @@ -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
Actually, this example does not necessarily disable vhost-user. It can work with vhost-user. I also notice that there are many comments inside this example to indicate it works with vhost-cuse. I think we need to correct this. By the way, vhost-cuse could be deprecated in the future, please refer here, http://dpdk.org/ml/archives/dev/2016-July/044080.html
Thanks,
Jianfeng
>
> After vhost is enabled and the implementation is selected, build the vhost
> library.
>
> --
> 1.9.3
next prev parent reply other threads:[~2016-07-20 1:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-19 15:32 Mark Kavanagh
2016-07-19 16:06 ` Mcnamara, John
2016-07-20 1:49 ` Tan, Jianfeng [this message]
2016-07-20 7:41 ` Kavanagh, Mark B
-- strict thread matches above, loose matches on Subject: below --
2016-07-19 15:23 Mark Kavanagh
2016-07-19 15:28 ` Kavanagh, Mark B
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=ED26CBA2FAD1BF48A8719AEF02201E3610621F9F@SHSMSX103.ccr.corp.intel.com \
--to=jianfeng.tan@intel.com \
--cc=dev@dpdk.org \
--cc=mark.b.kavanagh@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).