From: x-fn-spp@sl.ntt-tx.co.jp
To: ferruh.yigit@intel.com, yasufum.o@gmail.com
Cc: spp@dpdk.org
Subject: [spp] [PATCH 7/7] docs: fix incorrect commands in usecases.
Date: Thu, 9 Jan 2020 11:51:13 +0900 [thread overview]
Message-ID: <202001090251.0092pD8a027726@imss04.silk.ntt-tx.co.jp> (raw)
In-Reply-To: <20200109025113.22689-1-x-fn-spp@sl.ntt-tx.co.jp>
From: Hideyuki Yamashita <yamashita.hideyuki@po.ntt-tx.co.jp>
There are several incorrectness whih regards to
usecases, how to use parts.
So this patch set provides the fix.
Signed-off-by: Hideyuki Yamashita <yamashita.hideyuki@po.ntt-tx.co.jp>
Signed-off-by: Yasufumi Ogawa <yasufum.o@gmail.com>
---
docs/guides/gsg/howto_use.rst | 8 +++++---
docs/guides/usecases/multi_nodes.rst | 4 ++--
docs/guides/usecases/spp_nfv.rst | 2 +-
docs/guides/usecases/spp_vf.rst | 10 +++++-----
4 files changed, 13 insertions(+), 11 deletions(-)
diff --git a/docs/guides/gsg/howto_use.rst b/docs/guides/gsg/howto_use.rst
index 631594b..9553699 100644
--- a/docs/guides/gsg/howto_use.rst
+++ b/docs/guides/gsg/howto_use.rst
@@ -173,8 +173,9 @@ All of options can be referred with help option ``-h``.
.. code-block:: console
- python3 ./src/spp-ctl/spp-ctl -h
- usage: spp-ctl [-h] [-b BIND_ADDR] [-p PRI_PORT] [-s SEC_PORT] [-a API_PORT]
+ $ python3 ./src/spp-ctl/spp-ctl -h
+ usage: spp-ctl [-h] [-b BIND_ADDR] [-p PRI_PORT]
+ [-s SEC_PORT] [-a API_PORT]
SPP Controller
@@ -276,7 +277,7 @@ All of options can be referred with help option ``-h``.
.. code-block:: console
$ python3 src/spp.py -h
- usage: spp.py [-h] [-b BIND_ADDR] [-a API_PORT]
+ usage: spp.py [-h] [-b BIND_ADDR] [--config CONFIG]
SPP Controller
@@ -284,6 +285,7 @@ All of options can be referred with help option ``-h``.
-h, --help show this help message and exit
-b BIND_ADDR, --bind-addr BIND_ADDR
bind address, default=127.0.0.1:7777
+ --config CONFIG Config file path
All of SPP CLI commands are described in :doc:`../../commands/index`.
diff --git a/docs/guides/usecases/multi_nodes.rst b/docs/guides/usecases/multi_nodes.rst
index 3eaed0c..f61d6e9 100644
--- a/docs/guides/usecases/multi_nodes.rst
+++ b/docs/guides/usecases/multi_nodes.rst
@@ -173,8 +173,8 @@ Finally, change path from blue lines to red lines.
.. code-block:: console
# switch to server 1
- spp > server 2
- Switch spp-ctl to "2: 192.168.1.102:7777".
+ spp > server 1
+ Switch spp-ctl to "1: 192.168.1.101:7777".
# remove blue path
spp > nfv 1; stop
diff --git a/docs/guides/usecases/spp_nfv.rst b/docs/guides/usecases/spp_nfv.rst
index cc18b08..488fdec 100644
--- a/docs/guides/usecases/spp_nfv.rst
+++ b/docs/guides/usecases/spp_nfv.rst
@@ -385,7 +385,7 @@ to confirm that network on host is configured.
.. code-block:: console
- $ sudo $RE_SDK/examples/build/l2fwd -l 0-1 -- -p 0x03
+ $ sudo $RTE_SDK/examples/build/l2fwd -l 0-1 -- -p 0x03
.. _figure_spp_nfv_l2fwd_vhost:
diff --git a/docs/guides/usecases/spp_vf.rst b/docs/guides/usecases/spp_vf.rst
index f17c0dc..fda0b7d 100644
--- a/docs/guides/usecases/spp_vf.rst
+++ b/docs/guides/usecases/spp_vf.rst
@@ -194,14 +194,14 @@ First, delete entries of ``classifier_table`` and ports of components.
# forwarders
spp > vf 1; port del ring:0 rx fwd1
- spp > vf 1; port del vhost:0 tx fwd1
+ spp > vf 1; port del ring:2 tx fwd1
spp > vf 1; port del ring:1 rx fwd2
- spp > vf 1; port del vhost:2 tx fwd2
+ spp > vf 1; port del ring:3 tx fwd2
# mergers
spp > vf 1; port del ring:2 rx mgr
spp > vf 1; port del ring:3 rx mgr
- spp > vf 1; port del phy:0 tx mgr
+ spp > vf 1; port del phy:1 tx mgr
Then, stop components.
@@ -582,8 +582,8 @@ Delete entries from the table and ports from each of components.
spp > vf 1; port del vhost:3 tx fwd6
spp > vf 1; port del vhost:1 rx fwd7
spp > vf 1; port del ring:6 tx fwd7
- spp > vf 1; port del vhost:3 tx fwd8
- spp > vf 1; port del ring:7 rx fwd8
+ spp > vf 1; port del vhost:3 rx fwd8
+ spp > vf 1; port del ring:7 tx fwd8
# merger
spp > vf 1; port del ring:6 rx mgr2
--
2.17.1
prev parent reply other threads:[~2020-01-09 2:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200109025113.22689-1-x-fn-spp@sl.ntt-tx.co.jp>
2020-01-09 2:51 ` [spp] [PATCH 1/7] rcps: add vhost related rcps for spp_nfv x-fn-spp
2020-01-09 2:51 ` [spp] [PATCH 2/7] rcps: fix rcps for setting up spp_vf x-fn-spp
2020-01-09 2:51 ` [spp] [PATCH 3/7] rcps: fix typos " x-fn-spp
2020-01-09 2:51 ` [spp] [PATCH 4/7] rcps: fix rcps for shutting down spp_vf x-fn-spp
2020-01-09 2:51 ` [spp] [PATCH 5/7] rcps: add rcps for spp_mirror x-fn-spp
2020-01-09 2:51 ` [spp] [PATCH 6/7] docs: adds spp-vm1.xml x-fn-spp
2020-01-09 2:51 ` x-fn-spp [this message]
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=202001090251.0092pD8a027726@imss04.silk.ntt-tx.co.jp \
--to=x-fn-spp@sl.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).