From: ogawa.yasufumi@lab.ntt.co.jp
To: ferruh.yigit@intel.com, spp@dpdk.org, nakamura.hiroyuki@po.ntt-tx.co.jp
Cc: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
Subject: [spp] [PATCH 24/28] docs: fix incorrect descriptions of spp_vf
Date: Mon, 5 Feb 2018 11:46:20 +0900 [thread overview]
Message-ID: <20180205024620.8147-1-ogawa.yasufumi@lab.ntt.co.jp> (raw)
From: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
Correct descriptions for classifier_table command.
Signed-off-by: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
---
docs/guides/spp_vf/commands/secondary.rst | 2 +-
docs/guides/spp_vf/use_cases/usecase1.rst | 18 +++++++++---------
2 files changed, 10 insertions(+), 10 deletions(-)
diff --git a/docs/guides/spp_vf/commands/secondary.rst b/docs/guides/spp_vf/commands/secondary.rst
index bbbe69e..564e9af 100644
--- a/docs/guides/spp_vf/commands/secondary.rst
+++ b/docs/guides/spp_vf/commands/secondary.rst
@@ -207,7 +207,7 @@ to classifier table.
.. code-block:: console
- spp > sec 1;classifier_table add mac [MAC_ADDRESS] [RES_ID]
+ spp > sec [SEC_ID];classifier_table add mac [MAC_ADDRESS] [RES_ID]
This is an example to register an entry for port ``ring:0``.
diff --git a/docs/guides/spp_vf/use_cases/usecase1.rst b/docs/guides/spp_vf/use_cases/usecase1.rst
index d45011e..46726b4 100644
--- a/docs/guides/spp_vf/use_cases/usecase1.rst
+++ b/docs/guides/spp_vf/use_cases/usecase1.rst
@@ -177,15 +177,15 @@ MAC address and corresponging port is registered to the table with
.. code-block:: console
- spp > classifier_table add mac [MACADDRESS] [PORT]
+ spp > [SEC_ID];classifier_table add mac [MACADDRESS] [PORT]
In this usecase, you need to register two MAC addresses for merger1.
.. code-block:: console
# Register MAC address to classifier
- spp > classifier_table add mac 52:54:00:12:34:56 ring:0
- spp > classifier_table add mac 52:54:00:12:34:58 ring:1
+ spp > sec 1;classifier_table add mac 52:54:00:12:34:56 ring:0
+ spp > sec 1;classifier_table add mac 52:54:00:12:34:58 ring:1
Configuration for the second login path is almost similar to the first
@@ -232,8 +232,8 @@ Register entries to classifier_table for classifier2.
.. code-block:: console
# Register MAC address to classifier
- spp > classifier_table add mac 52:54:00:12:34:57 ring:4
- spp > classifier_table add mac 52:54:00:12:34:59 ring:5
+ spp > sec 1;classifier_table add mac 52:54:00:12:34:57 ring:4
+ spp > sec 1;classifier_table add mac 52:54:00:12:34:59 ring:5
Finally, activate all of settings by doign `flush` subcommand.
@@ -332,8 +332,8 @@ for the first SSH login path.
.. code-block:: console
# Delete MAC address from Classifier
- spp > classifier_table del mac 51:54:00:12:34:56 ring:0
- spp > classifier_table del mac 51:54:00:12:34:58 ring:1
+ spp > sec 1;classifier_table del mac 51:54:00:12:34:56 ring:0
+ spp > sec 1;classifier_table del mac 51:54:00:12:34:58 ring:1
.. code-block:: console
@@ -377,8 +377,8 @@ components.
.. code-block:: console
# Delete MAC address from Classifier
- spp > classifier_table del mac 51:54:00:12:34:57 ring:4
- spp > classifier_table del mac 51:54:00:12:34:59 ring:5
+ spp > sec 1;classifier_table del mac 51:54:00:12:34:57 ring:4
+ spp > sec 1;classifier_table del mac 51:54:00:12:34:59 ring:5
.. code-block:: console
--
2.13.1
reply other threads:[~2018-02-05 2:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20180205024620.8147-1-ogawa.yasufumi@lab.ntt.co.jp \
--to=ogawa.yasufumi@lab.ntt.co.jp \
--cc=ferruh.yigit@intel.com \
--cc=nakamura.hiroyuki@po.ntt-tx.co.jp \
--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).