From: ogawa.yasufumi@lab.ntt.co.jp
To: ferruh.yigit@intel.com, spp@dpdk.org, ogawa.yasufumi@lab.ntt.co.jp
Subject: [spp] [PATCH 4/7] docs: update spp_nfv commands
Date: Wed, 12 Dec 2018 11:03:29 +0900 [thread overview]
Message-ID: <1544580212-9309-5-git-send-email-ogawa.yasufumi@lab.ntt.co.jp> (raw)
In-Reply-To: <1544580212-9309-1-git-send-email-ogawa.yasufumi@lab.ntt.co.jp>
From: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
Update descriptions and examples to the latest release.
Signed-off-by: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
---
docs/guides/commands/secondary/spp_nfv.rst | 36 +++++++++++++++---------------
1 file changed, 18 insertions(+), 18 deletions(-)
diff --git a/docs/guides/commands/secondary/spp_nfv.rst b/docs/guides/commands/secondary/spp_nfv.rst
index 794ead5..4bc71a8 100644
--- a/docs/guides/commands/secondary/spp_nfv.rst
+++ b/docs/guides/commands/secondary/spp_nfv.rst
@@ -4,18 +4,18 @@
spp_nfv
=======
-Each of ``spp_nfv`` and ``spp_vm`` processes is managed with ``sec`` command.
+Each of ``spp_nfv`` and ``spp_vm`` processes is managed with ``nfv`` command.
It is for sending sub commands to secondary with specific ID called
secondary ID.
-``sec`` command takes an secondary ID and a sub command. They must be
+``nfv`` command takes an secondary ID and a sub command. They must be
separated with delimiter ``;``.
Some of sub commands take additional arguments for speicfying resource
owned by secondary process.
.. code-block:: console
- spp > sec SEC_ID; SUB_CMD
+ spp > nfv SEC_ID; SUB_CMD
All of Sub commands are referred with ``help`` command.
@@ -28,14 +28,14 @@ All of Sub commands are referred with ``help`` command.
SPP secondary process is specified with secondary ID and takes
sub commands.
- spp > sec 1; status
- spp > sec 1; add ring:0
- spp > sec 1; patch phy:0 ring:0
+ spp > nfv 1; status
+ spp > nfv 1; add ring:0
+ spp > nfv 1; patch phy:0 ring:0
You can refer all of sub commands by pressing TAB after
- 'sec 1;'.
+ 'nfv 1;'.
- spp > sec 1; # press TAB
+ spp > nfv 1; # press TAB
add del exit forward patch status stop
status
@@ -47,7 +47,7 @@ source if it is not patched.
.. code-block:: console
- spp > sec 1; status
+ spp > nfv 1; status
- status: idling
- ports:
- phy:0 -> ring:0
@@ -63,13 +63,13 @@ For example, adding ``ring:0`` by
.. code-block:: console
- spp> sec 1; add ring:0
+ spp> nfv 1; add ring:0
Or adding ``vhost:0`` by
.. code-block:: console
- spp> sec 1; add vhost:0
+ spp> nfv 1; add vhost:0
patch
@@ -80,7 +80,7 @@ This command just creates a path and does not start forwarding.
.. code-block:: console
- spp > sec 1; patch phy:0 ring:0
+ spp > nfv 1; patch phy:0 ring:0
forward
@@ -90,14 +90,14 @@ Start forwarding.
.. code-block:: console
- spp > sec 1; forward
+ spp > nfv 1; forward
Running status is changed from ``idling`` to ``running`` by
executing it.
.. code-block:: console
- spp > sec 1; status
+ spp > nfv 1; status
- status: running
- ports:
- phy:0
@@ -111,14 +111,14 @@ Stop forwarding.
.. code-block:: console
- spp > sec 1; stop
+ spp > nfv 1; stop
Running status is changed from ``running`` to ``idling`` by
executing it.
.. code-block:: console
- spp > sec 1; status
+ spp > nfv 1; status
- status: idling
- ports:
- phy:0
@@ -132,7 +132,7 @@ Delete a port from the secondary.
.. code-block:: console
- spp> sec 1; del ring:0
+ spp> nfv 1; del ring:0
exit
@@ -143,4 +143,4 @@ use ``bye sec`` command instead of it.
.. code-block:: console
- spp> sec 1; exit
+ spp> nfv 1; exit
--
2.7.4
next prev parent reply other threads:[~2018-12-12 2:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-12 2:03 [spp] [PATCH 0/7] Revise documentation for the latest release ogawa.yasufumi
2018-12-12 2:03 ` [spp] [PATCH 1/7] docs: update Getting Started section ogawa.yasufumi
2018-12-12 2:03 ` [spp] [PATCH 2/7] docs: update How to Use section ogawa.yasufumi
2018-12-12 2:03 ` [spp] [PATCH 3/7] docs: update Use Cases section ogawa.yasufumi
2018-12-12 2:03 ` ogawa.yasufumi [this message]
2018-12-12 2:03 ` [spp] [PATCH 5/7] docs: update Getting Started section of sppc ogawa.yasufumi
2018-12-12 2:03 ` [spp] [PATCH 6/7] docs: update Use Cases " ogawa.yasufumi
2018-12-12 2:03 ` [spp] [PATCH 7/7] recipes: update recipe files ogawa.yasufumi
2018-12-13 23:03 ` [spp] [PATCH v2 0/8] Revise documentation for the latest release ogawa.yasufumi
2018-12-13 23:03 ` [spp] [PATCH v2 1/8] docs: update Getting Started section ogawa.yasufumi
2018-12-13 23:03 ` [spp] [PATCH v2 2/8] docs: update How to Use section ogawa.yasufumi
2018-12-13 23:03 ` [spp] [PATCH v2 3/8] docs: update Use Cases section ogawa.yasufumi
2018-12-13 23:03 ` [spp] [PATCH v2 4/8] docs: update spp_nfv commands ogawa.yasufumi
2018-12-13 23:04 ` [spp] [PATCH v2 5/8] docs: update Getting Started section of sppc ogawa.yasufumi
2018-12-13 23:04 ` [spp] [PATCH v2 6/8] docs: update Use Cases " ogawa.yasufumi
2018-12-13 23:04 ` [spp] [PATCH v2 7/8] recipes: update recipe files ogawa.yasufumi
2018-12-13 23:04 ` [spp] [PATCH v2 8/8] docs: revise how to use section of spp_vf ogawa.yasufumi
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=1544580212-9309-5-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).