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>,
Daiki Yamashita <yamashita.daiki.z01@as.ntt-tx.co.jp>,
Naoki Takada <takada.naoki@lab.ntt.co.jp>
Subject: [spp] [PATCH 17/28] doc: add explanations on options of spp
Date: Tue, 23 Jan 2018 09:29:05 +0900 [thread overview]
Message-ID: <20180123002907.28414-8-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 the following explanations:
* Options for DPDK and ones for spp are available.
* Hyperlink to the reference to DPDK option is inserted.
Signed-off-by: Daiki Yamashita <yamashita.daiki.z01@as.ntt-tx.co.jp>
Signed-off-by: Naoki Takada <takada.naoki@lab.ntt.co.jp>
---
docs/spp_vf/how_to_use.md | 13 +++++++++++++
1 file changed, 13 insertions(+)
diff --git a/docs/spp_vf/how_to_use.md b/docs/spp_vf/how_to_use.md
index 6b5019c..e9b752d 100644
--- a/docs/spp_vf/how_to_use.md
+++ b/docs/spp_vf/how_to_use.md
@@ -29,6 +29,11 @@ $ python ./src/spp.py -p 5555 -s 6666
SPP primary reserves and manages resources for secondary processes.
You have to run it before secondaries.
+SPP primary has two kinds of options, dpdk and spp.
+Option of dpdk is before `--`, option of spp is after `--`.
+
+Option of dpdk are refer to [dpdk documentation](http://dpdk.org/doc/guides/linux_gsg/build_sample_apps.html#running-a-sample-application).
+
Options of spp primary are
* -p : port mask
* -n : number of rings
@@ -45,6 +50,14 @@ $ sudo ./src/primary/x86_64-native-linuxapp-gcc/spp_primary \
### SPP Secondary
In `spp_vf`, spp secondary processes are launched by single command.
+
+`spp_vf` has two kinds of options as well as spp primary.
+
+Option of dpdk are refer to [dpdk documentation](http://dpdk.org/doc/guides/linux_gsg/build_sample_apps.html#running-a-sample-application).
+
+Options of `spp_vf` are
+ * TODO
+
Core assingment and network configuration are defined
in JSON formatted config file.
If you run `spp_vf` without giving config file, it refers default
--
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 ` [spp] [PATCH 13/28] doc: update descriptions for todo ogawa.yasufumi
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 ` ogawa.yasufumi [this message]
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-8-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 \
--cc=yamashita.daiki.z01@as.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).