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 04/28] doc: add spp_vf.md
Date: Tue, 23 Jan 2018 09:28:49 +0900 [thread overview]
Message-ID: <20180123002854.28345-4-ogawa.yasufumi@lab.ntt.co.jp> (raw)
In-Reply-To: <20180123002854.28345-1-ogawa.yasufumi@lab.ntt.co.jp>
From: Hiroyuki Nakamura <nakamura.hioryuki@po.ntt-tx.co.jp>
This is a top level document for spp_vf. setup_guide or other
documents are refererd from it.
Signed-off-by: Naoki Takada <takada.naoki@lab.ntt.co.jp>
---
docs/spp_vf/spp_vf.md | 48 ++++++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 48 insertions(+)
create mode 100644 docs/spp_vf/spp_vf.md
diff --git a/docs/spp_vf/spp_vf.md b/docs/spp_vf/spp_vf.md
new file mode 100644
index 0000000..6587249
--- /dev/null
+++ b/docs/spp_vf/spp_vf.md
@@ -0,0 +1,48 @@
+# SPP_VF
+
+SPP_VF is a SR-IOV like network functionality using DPDK for NFV.
+
+![spp_vf_overview](spp_vf_overview.svg)
+
+## Overview
+
+The application distributes incoming packets depends on MAC address
+similar to SR-IOV functionality.
+Network configuration is defined in JSON config file which is imported
+while launching the application.
+The configuration is able to change by sending commnad from spp after
+initialization.
+
+SPP_VF is a multi-thread application.
+It consists of manager thread and forwarder threads.
+There are three types of forwarder for 1:1, 1:N and N:1.
+
+ * forward: 1:1
+ * classifier_mac: 1:N (Destination is determined by MAC address)
+ * merge: N:1
+
+This is an example of network configration, in which one classifier_mac,
+one merger and four forwarders are runnig in spp_vf process for two
+destinations of vhost interface.
+Incoming packets from rx on host1 are sent to each of vhosts on guest
+by looking MAC address in the packet..
+
+![spp_vf_overview](spp_vf_overview.svg)
+
+## Build the Application
+
+See [setup_guide](setup_guide.md).
+
+## Running the Application
+
+See [how_to_use](how_to_use.md).
+
+## Explanation
+
+The following sections provide some explanation of the code.
+
+### Configuration
+
+### Forwarding
+
+### Packet Cloning
--
2.13.1
next prev parent reply other threads:[~2018-01-23 0:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-23 0:28 [spp] [PATCH 01/28] doc: add setup guide ogawa.yasufumi
2018-01-23 0:28 ` [spp] [PATCH 02/28] doc: add how_to_use.md ogawa.yasufumi
2018-01-23 0:28 ` [spp] [PATCH 03/28] doc: add config_manual.md ogawa.yasufumi
2018-01-23 0:28 ` ogawa.yasufumi [this message]
2018-01-23 0:28 ` [spp] [PATCH 05/28] doc: revise spp_vf.md ogawa.yasufumi
2018-01-23 0:28 ` [spp] [PATCH 06/28] doc: add config section ogawa.yasufumi
2018-01-23 0:28 ` [spp] [PATCH 07/28] doc: update jp setup manual ogawa.yasufumi
2018-01-23 0:28 ` [spp] [PATCH 08/28] doc: modify figure in spp_vf_overview ogawa.yasufumi
2018-01-23 0:28 ` [spp] [PATCH 09/28] doc: add sample usage ogawa.yasufumi
2018-02-01 11:57 ` [spp] [PATCH 01/28] doc: add setup guide Ferruh Yigit
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=20180123002854.28345-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).