Soft Patch Panel
 help / color / mirror / Atom feed
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 <ogawa.yasufumi@lab.ntt.co.jp>
Subject: [spp] [PATCH 22/28] docs: update spp_vf design section
Date: Mon,  5 Feb 2018 11:42:38 +0900	[thread overview]
Message-ID: <20180205024238.7911-1-ogawa.yasufumi@lab.ntt.co.jp> (raw)

From: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>

Signed-off-by: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
---
 docs/guides/spp_vf/design.rst | 36 +++++++++++++++---------------------
 1 file changed, 15 insertions(+), 21 deletions(-)

diff --git a/docs/guides/spp_vf/design.rst b/docs/guides/spp_vf/design.rst
index 5938518..3c81134 100644
--- a/docs/guides/spp_vf/design.rst
+++ b/docs/guides/spp_vf/design.rst
@@ -36,7 +36,9 @@ Design
 Components
 ----------
 
-``spp_vf`` supports three types of components, ``forwarder``,
+``spp_vf`` is a kind of secondary process and consists of several
+threads called component.
+There are three types of components, ``forwarder``,
 ``merger`` and ``classifier``.
 
 .. image:: images/spp_vf_overview.svg
@@ -46,34 +48,26 @@ Components
 Forwarder
 ~~~~~~~~~
 
-This component provides function for packet processing from one port
-to one port.
-Incoming packets from port are to be transferred to specific one port.
-The direction of this transferring is specified by ``port`` command.
-The concept of port is described later of this section.
+Simply forwards packets from rx to tx port.
 
 Merger
 ~~~~~~
 
-This component provides packet forwarding function from multiple ports
-to one port.
-Incoming packets from multiple ports are to be transferred to one
-specific port.
-The flow of this merging process is specified by `port` command.
+Receives packets from multiple rx ports to aggregate
+packets and sends to a desctination port.
 
 Classifier
 ~~~~~~~~~~
 
-This component provides packet forwarding function from one port to
-one port.
-Classifier has table of virtual MAC address(A). According to this table,
-classifier lookups L2 destination MAC address and determines which port
-to be transferred to incoming packets.
-This component also supports vlan-tag(TPID:0x8100), and has the virtual
-MAC tables for each VID(B). If the TPID of incoming packet equals
-0x8100,
-then lookup these tables(B) and determines which port to be transferred.
-Otherwise, incoming packet is transferred according to table(A).
+Sends packets to multiple tx ports based on entries of
+MAC address and destination port in a classifier table.
+This component also supports VLAN tag.
+
+For VLAN addressing, classifier has other tables than defalut.
+Classifier prepares tables for each of VLAN ID and decides
+which of table is referred
+if TPID (Tag Protocol Indetifier) is included in a packet and
+equals to 0x8100 as defined in IEEE 802.1Q standard.
 
 
 Ports
-- 
2.13.1

                 reply	other threads:[~2018-02-05  2:42 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20180205024238.7911-1-ogawa.yasufumi@lab.ntt.co.jp \
    --to=ogawa.yasufumi@lab.ntt.co.jp \
    --cc=ferruh.yigit@intel.com \
    --cc=nakamura.hiroyuki@po.ntt-tx.co.jp \
    --cc=spp@dpdk.org \
    /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).