From: ogawa.yasufumi@lab.ntt.co.jp
To: spp@dpdk.org, ferruh.yigit@intel.com, ogawa.yasufumi@lab.ntt.co.jp
Subject: [spp] [PATCH 2/2] docs: fix typo of usecase of spp_mirror
Date: Wed, 20 Feb 2019 17:54:54 +0900 [thread overview]
Message-ID: <1550652894-2581-3-git-send-email-ogawa.yasufumi@lab.ntt.co.jp> (raw)
In-Reply-To: <1550652894-2581-1-git-send-email-ogawa.yasufumi@lab.ntt.co.jp>
From: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
Correct wrong `mir1` to `mir`, `minitor` to `monitor`.
Signed-off-by: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
---
docs/guides/usecases/spp_mirror.rst | 22 +++++++++++-----------
1 file changed, 11 insertions(+), 11 deletions(-)
diff --git a/docs/guides/usecases/spp_mirror.rst b/docs/guides/usecases/spp_mirror.rst
index dcb8e4d..5846bd1 100644
--- a/docs/guides/usecases/spp_mirror.rst
+++ b/docs/guides/usecases/spp_mirror.rst
@@ -94,17 +94,17 @@ Start mirror component with core ID 2.
.. code-block:: console
# terminal 2
- spp > mirror 1; component start mir1 2 mirror
+ spp > mirror 1; component start mir 2 mirror
Add ``phy:0`` as rx port, and ``phy:1`` and ``phy:2`` as tx ports.
.. code-block:: none
# terminal 2
- # add ports to mir1
- spp > mirror 1; port add phy:0 rx mir1
- spp > mirror 1; port add phy:1 tx mir1
- spp > mirror 1; port add phy:2 tx mir1
+ # add ports to mir
+ spp > mirror 1; port add phy:0 rx mir
+ spp > mirror 1; port add phy:1 tx mir
+ spp > mirror 1; port add phy:2 tx mir
Duplicate Packets
@@ -152,17 +152,17 @@ Delete ports for components.
.. code-block:: none
- # Delete port for mir1
- spp > mirror 1; port del phy:0 rx mir1
- spp > mirror 1; port del phy:1 tx mir1
- spp > mirror 1; port del phy:2 tx mir1
+ # Delete port for mir
+ spp > mirror 1; port del phy:0 rx mir
+ spp > mirror 1; port del phy:1 tx mir
+ spp > mirror 1; port del phy:2 tx mir
Next, stop components.
.. code-block:: console
# Stop mirror
- spp > mirror 1; component stop mir1 2 mirror
+ spp > mirror 1; component stop mir 2 mirror
spp > mirror 1; status
Basic Information:
@@ -186,7 +186,7 @@ Monitoring Packets
Duplicate classified packets for monitoring before going to a VM.
In this usecase, we are only interested in packets going to ``VM1``.
Although you might be able to run packet monitor app on host,
-run minitor on ``VM3`` considering more NFV like senario.
+run monitor on ``VM3`` considering more NFV like senario.
You use ``spp_mirror`` for copying, and ``spp_vf`` classifying packets.
.. _figure_usecase_monitor_overview:
--
2.17.1
prev parent reply other threads:[~2019-02-20 8:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-20 8:54 [spp] [PATCH 0/2] Revise docs ogawa.yasufumi
2019-02-20 8:54 ` [spp] [PATCH 1/2] docs: change use_cases to usecases ogawa.yasufumi
2019-02-20 8:54 ` ogawa.yasufumi [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=1550652894-2581-3-git-send-email-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).