From: ogawa.yasufumi@lab.ntt.co.jp
To: ferruh.yigit@intel.com, spp@dpdk.org
Cc: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
Subject: [spp] [PATCH 1/6] docs: add setting up PCAP
Date: Tue, 15 May 2018 10:21:41 +0900 [thread overview]
Message-ID: <20180515012146.8899-2-ogawa.yasufumi@lab.ntt.co.jp> (raw)
In-Reply-To: <20180515012146.8899-1-ogawa.yasufumi@lab.ntt.co.jp>
From: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
Signed-off-by: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
---
docs/guides/setup/getting_started.rst | 25 +++++++++++++++++++------
1 file changed, 19 insertions(+), 6 deletions(-)
diff --git a/docs/guides/setup/getting_started.rst b/docs/guides/setup/getting_started.rst
index 2b55d77..275e12f 100644
--- a/docs/guides/setup/getting_started.rst
+++ b/docs/guides/setup/getting_started.rst
@@ -159,7 +159,7 @@ For Linux, see `Getting Started Guide for Linux
DPDK
~~~~
-First, download and compile DPDK in any directory.
+Clone repository and compile DPDK in any directory.
.. code-block:: console
@@ -169,22 +169,35 @@ First, download and compile DPDK in any directory.
SPP provides libpcap-based PMD for dumping packet to a file or retrieve
it from the file.
-You should enable pcap while compiling DPDK because it is disabled as
-default.
-Compiling DPDK takes a few minutes.
+To use PCAP PMD, install ``libpcap-dev`` and enable it.
+
+.. code-block:: console
+
+ $ sudo apt install libpcap-dev
+
+PCAP is disabled by default in DPDK configuration.
+``CONFIG_RTE_LIBRTE_PMD_PCAP`` defines the configuration and enabled
+it to ``y``.
+
+.. code-block:: console
+
+ # dpdk/config/common_base
+ CONFIG_RTE_LIBRTE_PMD_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 CONFIG_RTE_LIBRTE_PMD_PCAP=y
+ $ make install T=$RTE_TARGET
SPP
~~~
-Then, download and compile SPP in any directory.
+Clone repository and compile SPP in any directory.
.. code-block:: console
--
2.17.0
next prev parent reply other threads:[~2018-05-15 1:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-15 1:21 [spp] [PATCH 0/6] Improve use of pcap PMD ogawa.yasufumi
2018-05-15 1:21 ` ogawa.yasufumi [this message]
2018-05-15 1:21 ` [spp] [PATCH 2/6] spp_nfv: update for creating rx pcap device ogawa.yasufumi
2018-05-15 1:21 ` [spp] [PATCH 3/6] docs: add installing text2pcap for pcap PMD ogawa.yasufumi
2018-05-15 1:21 ` [spp] [PATCH 4/6] docs: add usecase of " ogawa.yasufumi
2018-05-15 1:21 ` [spp] [PATCH 5/6] docs: add images of " ogawa.yasufumi
2018-05-15 1:21 ` [spp] [PATCH 6/6] docs: add references for images for " ogawa.yasufumi
2018-05-28 12:29 ` [spp] [PATCH 0/6] Improve use of " Ferruh Yigit
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=20180515012146.8899-2-ogawa.yasufumi@lab.ntt.co.jp \
--to=ogawa.yasufumi@lab.ntt.co.jp \
--cc=ferruh.yigit@intel.com \
--cc=spp@dpdk.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).