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>,
Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
Subject: [spp] [PATCH 26/28] doc: fix typos and erros in texts
Date: Tue, 23 Jan 2018 09:30:19 +0900 [thread overview]
Message-ID: <20180123003021.28557-7-ogawa.yasufumi@lab.ntt.co.jp> (raw)
In-Reply-To: <20180123003021.28557-1-ogawa.yasufumi@lab.ntt.co.jp>
From: Hiroyuki Nakamura <nakamura.hioryuki@po.ntt-tx.co.jp>
* config_manual.md: correct explanation of 'name' attribute.
* how_to_use.md: correct default config file path.
* how_to_use.md: correct titles.
* correct typos.
Signed-off-by: Daiki Yamashita <yamashita.daiki.z01@as.ntt-tx.co.jp>
Signed-off-by: Naoki Takada <takada.naoki@lab.ntt.co.jp>
Signed-off-by: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
---
docs/spp_vf/config_manual.md | 2 +-
docs/spp_vf/how_to_use.md | 8 ++++----
docs/spp_vf/setup_guide.md | 2 +-
3 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/docs/spp_vf/config_manual.md b/docs/spp_vf/config_manual.md
index 05a342c..cdf10b5 100644
--- a/docs/spp_vf/config_manual.md
+++ b/docs/spp_vf/config_manual.md
@@ -32,7 +32,7 @@ Config file consists of `vfs` and defines the spp_vf attribute.
### Attributes in Config
* vfs
- * name: Name of spp_vf component.
+ * name: Name of the configuration. Please set user as desired.
* num_vhost: Number of vhosts spp_vf use.
* num_ring: Number of rings spp_vf use.
* functions: List of forwarders and its attributes (function means a forwarder).
diff --git a/docs/spp_vf/how_to_use.md b/docs/spp_vf/how_to_use.md
index 32c1774..3d3e85a 100644
--- a/docs/spp_vf/how_to_use.md
+++ b/docs/spp_vf/how_to_use.md
@@ -64,7 +64,7 @@ Options of `spp_vf` are
Core assingment and network configuration are defined
in JSON formatted config file.
If you run `spp_vf` without giving config file, it refers default
-config file (test/spp_config/spp_config/vf.json).
+config file (/usr/local/etc/spp/spp.json).
```sh
$ sudo ./src/vf/x86_64-native-linuxapp-gcc/spp_vf \
@@ -97,7 +97,7 @@ $ sudo ./src/vf/x86_64-native-linuxapp-gcc/spp_vf \
-s 127.0.0.1:6666 --vhost-client
```
-### SPP VM
+### VM
Launch VMs with `virsh` command.
@@ -108,9 +108,9 @@ $ virsh start [VM]
### Additional Network Configurations
To enable processes running on the VM to communicate through spp,
-it is required additional network configurations on host and guest VMss.
+it is required additional network configurations on host and guest VMs.
-#### Host1
+#### Guest VMs
```sh
# Interface for vhost
diff --git a/docs/spp_vf/setup_guide.md b/docs/spp_vf/setup_guide.md
index af2e9bf..a20ae90 100644
--- a/docs/spp_vf/setup_guide.md
+++ b/docs/spp_vf/setup_guide.md
@@ -73,7 +73,7 @@ Finally, you unmount default hugepage.
$ sudo unmount /dev/hugepages
```
-#### Install jasson
+#### Install jansson
Network configuration is defined in JSON and `spp_vf` reads config from
the file while launching.
--
2.13.1
next prev parent reply other threads:[~2018-01-23 0:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-23 0:30 [spp] [PATCH 20/28] doc: fix vm setup procedure for network config ogawa.yasufumi
2018-01-23 0:30 ` [spp] [PATCH 21/28] doc: update jansson installation procedure ogawa.yasufumi
2018-01-23 0:30 ` [spp] [PATCH 22/28] doc: fix required network configuration ogawa.yasufumi
2018-01-23 0:30 ` [spp] [PATCH 23/28] doc: add how to use vhost-user support ogawa.yasufumi
2018-01-23 0:30 ` [spp] [PATCH 24/28] doc: add references to hugepages and isolcpus ogawa.yasufumi
2018-01-23 0:30 ` [spp] [PATCH 25/28] doc: remove description on classifier_table ogawa.yasufumi
2018-01-23 0:30 ` ogawa.yasufumi [this message]
2018-01-23 0:30 ` [spp] [PATCH 27/28] doc: update sample config section ogawa.yasufumi
2018-01-23 0:30 ` [spp] [PATCH 28/28] doc: align figure title position 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=20180123003021.28557-7-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).