From: x-fn-spp-ml@ntt-tx.co.jp
To: spp@dpdk.org, ferruh.yigit@intel.com, yasufum.o@gmail.com
Subject: [spp] [PATCH v2 02/11] docs: add support of MLX5 PMD support in DPDK
Date: Fri, 27 Mar 2020 13:57:23 +0900 [thread overview]
Message-ID: <20200327045732.18463-3-x-fn-spp-ml@ntt-tx.co.jp> (raw)
In-Reply-To: <20200226113521.3787-1-x-fn-spp-ml@ntt-tx.co.jp>
From: Hideyuki Yamashita <yamashita.hideyuki@ntt-tx.co.jp>
This patch adds configuration change of DPDK
to support MLX5 PMD in DPDK compilation.
Signed-off-by: Hideyuki Yamashita <yamashita.hideyuki@ntt-tx.co.jp>
Signed-off-by: Naoki Takada <ntakada14@gmail.com>
---
docs/guides/gsg/install.rst | 25 +++++--------------------
1 file changed, 5 insertions(+), 20 deletions(-)
diff --git a/docs/guides/gsg/install.rst b/docs/guides/gsg/install.rst
index 335a151..2abf330 100644
--- a/docs/guides/gsg/install.rst
+++ b/docs/guides/gsg/install.rst
@@ -129,29 +129,15 @@ config file ``common_base`` should be changed to ``y`` to enable PCAP.
...
CONFIG_RTE_PORT_PCAP=y
-Compile DPDK with target environment.
-
-.. code-block:: console
-
- $ cd dpdk
- $ export RTE_SDK=$(pwd)
- $ export RTE_TARGET=x86_64-native-linuxapp-gcc # depends on your env
- $ make install T=$RTE_TARGET
-
+If you use MLX5 NIC, ``CONFIG_RTE_LIBRTE_MLX5_PMD`` defined in
+config file ``common_base`` should be changed to ``y``.
-PCAP is disabled by default in DPDK configuration, so should be changed
-if you use this feature.
-``CONFIG_RTE_LIBRTE_PMD_PCAP`` and ``CONFIG_RTE_PORT_PCAP`` defined in
-config file ``common_base`` should be changed to ``y`` to enable PCAP.
-
-.. code-block:: console
+.. code-block:: none
# dpdk/config/common_base
- CONFIG_RTE_LIBRTE_PMD_PCAP=y
- ...
- CONFIG_RTE_PORT_PCAP=y
+ CONFIG_RTE_LIBRTE_MLX5_PMD=y
-Compile DPDK with options for target environment.
+Compile DPDK with target environment.
.. code-block:: console
@@ -160,7 +146,6 @@ Compile DPDK with options for target environment.
$ export RTE_TARGET=x86_64-native-linuxapp-gcc # depends on your env
$ make install T=$RTE_TARGET
-
Pyhton
------
--
2.17.1
next prev parent reply other threads:[~2020-03-27 4:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200226113521.3787-1-x-fn-spp-ml@ntt-tx.co.jp>
2020-03-27 4:57 ` [spp] [PATCH v2 00/11] Add Hardware offload document x-fn-spp-ml
2020-03-27 4:57 ` [spp] [PATCH v2 01/11] docs: add support for rte_flow x-fn-spp-ml
2020-03-27 4:57 ` x-fn-spp-ml [this message]
2020-03-27 4:57 ` [spp] [PATCH v2 03/11] docs: change primary process startup parameter x-fn-spp-ml
2020-03-27 4:57 ` [spp] [PATCH v2 04/11] docs: add description of REST-APIs for flow rules x-fn-spp-ml
2020-03-27 4:57 ` [spp] [PATCH v2 05/11] docs: support flow syntax in primary command x-fn-spp-ml
2020-03-27 4:57 ` [spp] [PATCH v2 06/11] docs: support multi-queue in spp_vf command x-fn-spp-ml
2020-03-27 4:57 ` [spp] [PATCH v2 07/11] docs: add svg for classify case of hardware offload x-fn-spp-ml
2020-03-27 4:57 ` [spp] [PATCH v2 08/11] docs: add svg for vlan " x-fn-spp-ml
2020-03-27 4:57 ` [spp] [PATCH v2 09/11] docs: add svg for vm " x-fn-spp-ml
2020-03-27 4:57 ` [spp] [PATCH v2 10/11] docs: add usecase for " x-fn-spp-ml
2020-03-27 4:57 ` [spp] [PATCH v2 11/11] docs: add install drivers for Mellanox NIC x-fn-spp-ml
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=20200327045732.18463-3-x-fn-spp-ml@ntt-tx.co.jp \
--to=x-fn-spp-ml@ntt-tx.co.jp \
--cc=ferruh.yigit@intel.com \
--cc=spp@dpdk.org \
--cc=yasufum.o@gmail.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).