From: ogawa.yasufumi@lab.ntt.co.jp
To: spp@dpdk.org, ferruh.yigit@intel.com, x-fn-spp@sl.ntt-tx.co.jp
Cc: Hiroyuki Nakamura <nakamura.hioryuki@po.ntt-tx.co.jp>,
Naoki Takada <takada.naoki@lab.ntt.co.jp>
Subject: [spp] [PATCH 13/28] doc: update descriptions for todo
Date: Tue, 23 Jan 2018 09:29:01 +0900 [thread overview]
Message-ID: <20180123002907.28414-4-ogawa.yasufumi@lab.ntt.co.jp> (raw)
In-Reply-To: <20180123002907.28414-1-ogawa.yasufumi@lab.ntt.co.jp>
From: Hiroyuki Nakamura <nakamura.hioryuki@po.ntt-tx.co.jp>
- Add why use nc command and how.
- Change the status of json based steps from 'are deprecated' to
'will be deprecated'.
Signed-off-by: Naoki Takada <takada.naoki@lab.ntt.co.jp>
---
docs/spp_vf/sample_usage.md | 14 ++++++++++----
1 file changed, 10 insertions(+), 4 deletions(-)
diff --git a/docs/spp_vf/sample_usage.md b/docs/spp_vf/sample_usage.md
index 00e1631..ce68867 100644
--- a/docs/spp_vf/sample_usage.md
+++ b/docs/spp_vf/sample_usage.md
@@ -34,10 +34,16 @@ First, launch spp controller and primary process.
-p 0x03 -n 8 -s 127.0.0.1:5555
```
-TODO(yasufum) add description for sec.
+After primary process is launched, run nc command for each of
+seconrdary processes and itselves.
+In this sample, commands for secondary are sent from nc because
+`spp.py` does not support commands for spp_vf.
+nc is a network utility and it can open TCP connections, send UDP
+packets, listen on arbitrary TCP and UDP ports, do port scanning,
+and deal with both IPv4 and IPv6.
```sh
- # start nc for secondary 1
+ # run nc for secondary 1 with port 11111
$ while true; do nc -l 11111; done
# start secondary 1
@@ -48,7 +54,7 @@ TODO(yasufum) add description for sec.
--config /path/to/spp_vf1_without_cmtab.json \
-s 127.0.0.1:11111
- # start nc for secondary 2
+ # run nc for secondary 2 with port 11112
$ while true; do nc -l 11112; done
# start secondary 2
@@ -120,7 +126,7 @@ discarding packets.
## Test Application
-TODO(yasufum) json-based steps are deprecated.
+TODO(yasufum) json-based steps will be deprecated.
### Register MAC address to Classifier
--
2.13.1
next prev parent reply other threads:[~2018-01-23 0:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-23 0:28 [spp] [PATCH 10/28] doc: revice path descs ogawa.yasufumi
2018-01-23 0:28 ` [spp] [PATCH 11/28] doc: add network configuration diagram ogawa.yasufumi
2018-01-23 0:29 ` [spp] [PATCH 12/28] doc: update user account ogawa.yasufumi
2018-01-23 0:29 ` ogawa.yasufumi [this message]
2018-01-23 0:29 ` [spp] [PATCH 14/28] doc: add description for explanation section ogawa.yasufumi
2018-01-23 0:29 ` [spp] [PATCH 15/28] doc: add spp_sample_usage_svg in docs/spp_vf/ ogawa.yasufumi
2018-01-23 0:29 ` [spp] [PATCH 16/28] doc: add explanation for terminating spp app ogawa.yasufumi
2018-01-23 0:29 ` [spp] [PATCH 17/28] doc: add explanations on options of spp ogawa.yasufumi
2018-01-23 0:29 ` [spp] [PATCH 18/28] doc: update description for the latest spp version 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=20180123002907.28414-4-ogawa.yasufumi@lab.ntt.co.jp \
--to=ogawa.yasufumi@lab.ntt.co.jp \
--cc=ferruh.yigit@intel.com \
--cc=nakamura.hioryuki@po.ntt-tx.co.jp \
--cc=spp@dpdk.org \
--cc=takada.naoki@lab.ntt.co.jp \
--cc=x-fn-spp@sl.ntt-tx.co.jp \
/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).