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 11/28] doc: add network configuration diagram
Date: Tue, 23 Jan 2018 09:28:59 +0900 [thread overview]
Message-ID: <20180123002907.28414-2-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>
Signed-off-by: Naoki Takada <takada.naoki@lab.ntt.co.jp>
---
docs/spp_vf/sample_usage.md | 2 ++
1 file changed, 2 insertions(+)
diff --git a/docs/spp_vf/sample_usage.md b/docs/spp_vf/sample_usage.md
index 5f6ece2..bb4d540 100644
--- a/docs/spp_vf/sample_usage.md
+++ b/docs/spp_vf/sample_usage.md
@@ -7,6 +7,8 @@ It enables to access to VMs with ssh from a remote node.
Before trying this sample, install SPP by following
[setup guide](setup_guide.md).
+![spp_sample_usage](spp_sample_usage.svg)
+
## Testing Steps
In this section, you configure spp_vf and client applications for
--
2.13.1
next prev parent reply other threads:[~2018-01-23 0:28 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 ` ogawa.yasufumi [this message]
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 ` [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-2-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).