From: ogawa.yasufumi@lab.ntt.co.jp
To: ferruh.yigit@intel.com
Cc: spp@dpdk.org, Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
Subject: [spp] [PATCH v2 3/3] docs: add description for python 3 support
Date: Thu, 24 May 2018 05:11:50 +0900 [thread overview]
Message-ID: <20180523201150.23042-4-ogawa.yasufumi@lab.ntt.co.jp> (raw)
In-Reply-To: <20180523201150.23042-1-ogawa.yasufumi@lab.ntt.co.jp>
From: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
Add description to explain that SPP controller supports Python 3 while
keeping compatibility for Python 2.
Signed-off-by: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
---
docs/guides/setup/getting_started.rst | 17 +++++++++++++++--
1 file changed, 15 insertions(+), 2 deletions(-)
diff --git a/docs/guides/setup/getting_started.rst b/docs/guides/setup/getting_started.rst
index 04df517..75dc68d 100644
--- a/docs/guides/setup/getting_started.rst
+++ b/docs/guides/setup/getting_started.rst
@@ -120,6 +120,9 @@ Refer to `DPDK documentation
For Linux, see `Getting Started Guide for Linux
<http://www.dpdk.org/doc/guides/linux_gsg/index.html>`_ .
+DPDK
+~~~~
+
First, download and compile DPDK in any directory.
Compiling DPDK takes a few minutes.
@@ -132,6 +135,9 @@ Compiling DPDK takes a few minutes.
$ export RTE_TARGET=x86_64-native-linuxapp-gcc # depends on your env
$ make install T=$RTE_TARGET
+SPP
+~~~
+
Then, download and compile SPP in any directory.
.. code-block:: console
@@ -142,6 +148,13 @@ Then, download and compile SPP in any directory.
$ make # Confirm that $RTE_SDK and $RTE_TARGET are set
+Python 2 or 3 ?
+~~~~~~~~~~~~~~~
+
+You need to install Python for using usertools of DPDK or SPP controller.
+DPDK and SPP support both of Python2 and 3.
+
+
Binding Network Ports to DPDK
-----------------------------
@@ -238,8 +251,8 @@ cannot find it by using ``ifconfig`` or ``ip``.
....
-Run DPDK Sample Application
----------------------------
+Confirm DPDK is setup properly
+------------------------------
You had better to run DPDK sample application before SPP
as checking DPDK is setup properly.
--
2.17.0
next prev parent reply other threads:[~2018-05-23 20:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-15 1:20 [spp] [PATCH 0/3] Update for Python " ogawa.yasufumi
2018-05-15 1:20 ` [spp] [PATCH 1/3] controller: change importing for python3 ogawa.yasufumi
2018-05-15 1:20 ` [spp] [PATCH 2/3] controller: fix encoding for socket ogawa.yasufumi
2018-05-15 1:20 ` [spp] [PATCH 3/3] docs: add description for python 3 support ogawa.yasufumi
2018-05-23 20:11 ` [spp] [PATCH v2 0/3] Update for Python " ogawa.yasufumi
2018-05-23 20:11 ` [spp] [PATCH v2 1/3] controller: change importing for python3 ogawa.yasufumi
2018-05-23 20:11 ` [spp] [PATCH v2 2/3] controller: fix encoding for socket ogawa.yasufumi
2018-05-23 20:11 ` ogawa.yasufumi [this message]
2018-05-24 13:18 ` [spp] [PATCH v2 0/3] Update for Python 3 support 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=20180523201150.23042-4-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).