From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mogw0622.ocn.ad.jp (mogw0622.ocn.ad.jp [153.149.228.23]) by dpdk.org (Postfix) with ESMTP id 54CCE1B1AA for ; Mon, 5 Feb 2018 03:38:55 +0100 (CET) Received: from mf-smf-ucb016.ocn.ad.jp (mf-smf-ucb016.ocn.ad.jp [153.149.231.3]) by mogw0622.ocn.ad.jp (Postfix) with ESMTP id A36FB4800F3; Mon, 5 Feb 2018 11:38:53 +0900 (JST) Received: from mf-smf-ucb016.ocn.ad.jp (mf-smf-ucb016 [153.149.231.3]) by mf-smf-ucb016.ocn.ad.jp (Postfix) with ESMTP id 8D8C1100624; Mon, 5 Feb 2018 11:38:53 +0900 (JST) Received: from ntt.pod01.mv-mta-ucb024 (mv-mta-ucb024.ocn.ad.jp [153.149.142.98]) by mf-smf-ucb016.ocn.ad.jp (Switch-3.3.4/Switch-3.3.4) with ESMTP id w152ckdf006436; Mon, 5 Feb 2018 11:38:53 +0900 Received: from smtp.ocn.ne.jp ([153.149.227.134]) by ntt.pod01.mv-mta-ucb024 with id 6qes1x00A2ud8JZ01qesvF; Mon, 05 Feb 2018 02:38:53 +0000 Received: from localhost.localdomain (sp49-97-109-142.msc.spmode.ne.jp [49.97.109.142]) by smtp.ocn.ne.jp (Postfix) with ESMTPA; Mon, 5 Feb 2018 11:38:52 +0900 (JST) From: ogawa.yasufumi@lab.ntt.co.jp To: ferruh.yigit@intel.com, spp@dpdk.org, nakamura.hiroyuki@po.ntt-tx.co.jp Cc: Yasufumi Ogawa Date: Mon, 5 Feb 2018 11:38:56 +0900 Message-Id: <20180205023921.7775-3-ogawa.yasufumi@lab.ntt.co.jp> X-Mailer: git-send-email 2.13.1 In-Reply-To: <20180205023921.7775-1-ogawa.yasufumi@lab.ntt.co.jp> References: <20180205023921.7775-1-ogawa.yasufumi@lab.ntt.co.jp> Subject: [spp] [PATCH 03/28] docs: add spp_vf overview X-BeenThere: spp@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Soft Patch Panel List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Feb 2018 02:38:57 -0000 From: Yasufumi Ogawa Signed-off-by: Yasufumi Ogawa --- .../spp_vf/{getting_started => gsg}/index.rst | 0 docs/guides/spp_vf/images/spp_vf_overview.svg | 1944 ++++++++++++++++++++ docs/guides/spp_vf/overview.rst | 26 +- 3 files changed, 1969 insertions(+), 1 deletion(-) rename docs/guides/spp_vf/{getting_started => gsg}/index.rst (100%) create mode 100644 docs/guides/spp_vf/images/spp_vf_overview.svg diff --git a/docs/guides/spp_vf/getting_started/index.rst b/docs/guides/spp_vf/gsg/index.rst similarity index 100% rename from docs/guides/spp_vf/getting_started/index.rst rename to docs/guides/spp_vf/gsg/index.rst diff --git a/docs/guides/spp_vf/images/spp_vf_overview.svg b/docs/guides/spp_vf/images/spp_vf_overview.svg new file mode 100644 index 0000000..3b1ae68 --- /dev/null +++ b/docs/guides/spp_vf/images/spp_vf_overview.svg @@ -0,0 +1,1944 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + image/svg+xml + + + + + + + + host1 + + NIC + + host2 + + NIC + + + + + + + + + + + network + + + + spp_vf + + + + guest vm1 + + guest vm2 + + vNIC + + vNIC + + + + + + ring + + classifier + + + + vhost + + + + + + + + + + + merger + + + forwarder + + + + forwarder + + + + forwarder + + + + forwarder + + + + + ring + + ring + + + + + ring + + ring + + + traffic generator + + + + app2 + + + + app1 + + + + + + vhost + + + + + + ring + + ring + + + + + ring + + ring + + + diff --git a/docs/guides/spp_vf/overview.rst b/docs/guides/spp_vf/overview.rst index e6f83ea..f1a1714 100644 --- a/docs/guides/spp_vf/overview.rst +++ b/docs/guides/spp_vf/overview.rst @@ -32,4 +32,28 @@ Overview ======== -SPP_VF +SPP_VF provides SR-IOV like network functionality using DPDK for NFV. + +PP_VF distributes incoming packets to VMs with referring to virtual +MAC address like Virtual Function(VF) of SR-IOV. +Virtual MAC address can be defined by commands from spp +controller(``spp_vf.py``). + +SPP_VF is multi-process and multi-thread applications. A SPP_VF process +is referred to as ``spp_vf`` in this document. Each ``spp_vf`` has +one manager thread and component threads. The manager thread provides +function for command processing and creating the component threads. +The component threads have its own multiple components, ports and +classifier tables including Virtual MAC address. + + +This is an example of network configuration, in which one +``classifier_mac``, +one merger and four forwarders are running in SPP_VF process +for two destinations of vhost interface. +Incoming packets from rx on host1 are sent to each of vhosts of VM +by looking up destination MAC address in the packet. + +.. image:: images/spp_vf_overview.svg + :height: 550 em + :width: 550 em -- 2.13.1