From: ogawa.yasufumi@lab.ntt.co.jp
To: spp@dpdk.org, ferruh.yigit@intel.com
Cc: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
Subject: [spp] [PATCH 12/15] docs: update use_cases section
Date: Thu, 1 Feb 2018 13:04:58 +0900 [thread overview]
Message-ID: <20180201040501.8004-12-ogawa.yasufumi@lab.ntt.co.jp> (raw)
In-Reply-To: <20180201040501.8004-1-ogawa.yasufumi@lab.ntt.co.jp>
From: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
* Update descriptions for old version of SPP which is not supported
currently.
* Add explanation for configuring ring pmd and vhost pmd.
* Revise whole descriptions.
Signed-off-by: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
---
docs/guides/setup/use_cases.rst | 437 +++++++++++++++++++++++++++++++++++++++-
1 file changed, 436 insertions(+), 1 deletion(-)
diff --git a/docs/guides/setup/use_cases.rst b/docs/guides/setup/use_cases.rst
index fcff8d2..3b59498 100644
--- a/docs/guides/setup/use_cases.rst
+++ b/docs/guides/setup/use_cases.rst
@@ -29,4 +29,439 @@
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Use Cases
-===============================
+=========
+
+.. _single_spp_nfv:
+
+Single spp_nfv
+--------------
+
+The most simple use case mainly for testing performance of packet
+forwarding on host.
+One ``spp_nfv`` and two physical ports.
+
+In this use case, try to configure two senarios.
+
+- Configure spp_nfv as L2fwd
+- Configure spp_nfv for Loopback
+
+
+First of all, Check the status of ``spp_nfv`` from SPP controller.
+
+.. code-block:: console
+
+ spp > sec 1;status
+ recv:6:{Client ID 1 Idling
+ 1
+ port id: 0,on,PHY,outport: -99
+ port id: 1,on,PHY,outport: -99
+ }
+
+This message explains that ``sec 1`` has two physical ports refered as
+port id 0 and 1.
+``outpport: -99`` means that destionation port is not assigned.
+
+
+Configure spp_nfv as L2fwd
+~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Assing the destination of ports with ``patch`` subcommand and
+start forwarding.
+Patch from ``port 0`` to ``port 1`` and ``port 1`` to ``port 0``,
+which means it is bi-directional connection.
+
+.. code-block:: console
+
+ spp > sec 1;patch 0 1
+ spp > sec 1;patch 1 0
+ spp > sec 1;forward
+
+Confirm that status of ``sec 1`` is updated.
+
+.. code-block:: console
+
+ spp > sec 1;status
+ recv:6:{Client ID 1 Running
+ 1
+ port id: 0,on,PHY,outport: 1
+ port id: 1,on,PHY,outport: 0
+ }
+
+.. code-block:: console
+
+ __
+ +--------------+ |
+ | spp_nfv | |
+ | (sec 1) | |
+ +--------------+ |
+ ^ : |
+ | | |
+ : v |
+ +----+----------+-------------------------------------------------+ |
+ | | primary | ^ : | |
+ | +----------+ : : | |
+ | : : | |
+ | +----------+ +---------+ | | host
+ | : v | |
+ | +--------------+ +--------------+ | |
+ | | phy port 0 | | phy port 1 | | |
+ +------------------+--------------+------------+--------------+---+ __|
+ ^ :
+ | |
+ : v
+
+Stop forwarding and reset patch to clear configuration.
+
+.. code-block:: console
+
+ spp > sec 1;stop
+ spp > sec 1;patch reset
+
+
+Configure spp_nfv for Loopback
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Patch ``port 0`` to ``port 0`` and ``port 1`` to ``port 1``
+for loopback.
+
+.. code-block:: console
+
+ spp > sec 1;patch 0 0
+ spp > sec 1;patch 1 1
+ spp > sec 1;forward
+
+
+Dual spp_nfv
+------------
+
+Use case for testing performance of packet forwarding
+with two ``spp_nfv`` on host.
+Throughput is expected to be better than
+:ref:`Single spp_nfv<single_spp_nfv>`
+use case
+because bi-directional forwarding of single nfv shared with two of
+uni-directional forwarding between dual spp_nfv.
+
+In this use case, configure two senarios almost similar to
+previous section.
+
+- Configure Two spp_nfv as L2fwd
+- Configure Two spp_nfv for Loopback
+
+
+Configure Two spp_nfv as L2fwd
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Assing the destination of ports with ``patch`` subcommand and
+start forwarding.
+Patch from ``port 0`` to ``port 1`` for ``sec 1`` and
+from ``port 1`` to ``port 0`` for ``sec 2``.
+
+.. code-block:: console
+
+ spp > sec 1;patch 0 1
+ spp > sec 2;patch 1 0
+ spp > sec 1;forward
+ spp > sec 2;forward
+
+.. code-block:: console
+
+ __
+ +--------------+ +--------------+ |
+ | spp_nfv | | spp_nfv | |
+ | (sec 1) | | (sec 2) | |
+ +--------------+ +--------------+ |
+ ^ : : : |
+ | | +--------+ | |
+ : v | v |
+ +----+----------+-----------------------+-------------------------+ |
+ | | primary | ^ : | : | |
+ | +----------+ | +------+--------+ : | |
+ | : | : : | |
+ | : +------+ : | | | host
+ | : v v v | |
+ | +--------------+ +--------------+ | |
+ | | phy port 0 | | phy port 1 | | |
+ +------------------+--------------+------------+--------------+---+ __|
+ ^ :
+ | |
+ : v
+
+
+Configure two spp_nfv for Loopback
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Patch ``port 0`` to ``port 0`` for ``sec 1`` and
+``port 1`` to ``port 1`` for ``sec 2`` for loopback.
+
+.. code-block:: console
+
+ spp > sec 1;patch 0 0
+ spp > sec 2;patch 1 1
+ spp > sec 1;forward
+ spp > sec 2;forward
+
+.. code-block:: console
+
+ __
+ +--------------+ +--------------+ |
+ | spp_nfv | | spp_nfv | |
+ | (sec 1) | | (sec 2) | |
+ +--------------+ +--------------+ |
+ ^ : ^ : |
+ | | | | |
+ : v : v |
+ +----+----------+-------------------------------------------------+ |
+ | | primary | ^ : ^ : | |
+ | +----------+ | : | : | |
+ | : : : : | |
+ | : | : | | | host
+ | : v : v | |
+ | +--------------+ +--------------+ | |
+ | | phy port 0 | | phy port 1 | | |
+ +------------------+--------------+------------+--------------+---+ __|
+ ^ ^
+ | |
+ v v
+
+
+Dual spp_nfv with Ring PMD
+--------------------------
+
+In this use case, configure two senarios by using ring PMD.
+
+- Uni-Directional L2fwd
+- Bi-Directional L2fwd
+
+Ring PMD
+~~~~~~~~
+
+Ring PMD is an interface for communicating between secondaries on host.
+The maximum number of ring PMDs is defined as ``-n`` option of
+``spp_primary`` and ring ID is started from 0.
+
+A reference of a ring PMD is added by using ``add`` subcommand.
+All of ring PMDs is showed by ``status`` subcommand.
+
+.. code-block:: console
+
+ spp > sec 1;add ring 0
+ recv:6:{addring0}
+ spp > sec 1;status
+ recv:6:{Client ID 1 Idling
+ 1
+ port id: 0,on,PHY,outport: -99
+ port id: 1,on,PHY,outport: -99
+ port id: 2,on,RING(0),outport: -99
+ }
+
+Notice that ring 0 is added to ``sec 1`` and it is referred as
+port id 2.
+
+To clear the configuration, delete ``ring 0``.
+
+.. code-block:: console
+
+ spp > sec 1;del ring 0
+ recv:6:{delring0}
+ spp > sec 1;status
+ recv:6:{Client ID 1 Idling
+ 1
+ port id: 0,on,PHY,outport: -99
+ port id: 1,on,PHY,outport: -99
+ }
+
+
+Uni-Directional L2fwd
+~~~~~~~~~~~~~~~~~~~~~
+
+Add a ring PMD and connect two ``spp_nvf`` processes.
+To configure network path, add ``ring 0`` to ``sec 1`` and ``sec 2``.
+Then, connect it with ``patch`` subcommand.
+
+.. code-block:: console
+
+ spp > sec 1;add ring 0
+ spp > sec 2;add ring 0
+ spp > sec 1;patch 0 2
+ spp > sec 2;patch 2 1
+ spp > sec 1;forward
+ spp > sec 2;forward
+
+.. code-block:: console
+
+ __
+ +----------+ ring 0 +----------+ |
+ | spp_nfv | +--------+ | spp_nfv | |
+ | (sec 1) | -> | | | |- > | (sec 2) | |
+ +----------+ +--------+ +----------+ |
+ ^ : |
+ | | |
+ : v |
+ +----+----------+-------------------------------------------------+ |
+ | | primary | ^ : | |
+ | +----------+ | : | |
+ | : : | |
+ | : | | | host
+ | : v | |
+ | +--------------+ +--------------+ | |
+ | | phy port 0 | | phy port 1| | |
+ +------------------+--------------+------------+--------------+---+ __|
+ ^ :
+ | |
+ : v
+
+
+Bi-Directional L2fwd
+~~~~~~~~~~~~~~~~~~~~
+
+Add two ring PMDs to two ``spp_nvf`` processes.
+For bi-directional forwarding,
+patch ``ring 0`` for a path from ``sec 1`` to ``sec 2``
+and ``ring 1`` for another path from ``sec 2`` to ``sec 1``.
+
+First, add ``ring 0`` and ``ring 1`` to ``sec 1``.
+
+.. code-block:: console
+
+ spp > sec 1;add ring 0
+ spp > sec 1;add ring 1
+ spp > sec 1;status
+ recv:6:{Client ID 1 Idling
+ 1
+ port id: 0,on,PHY,outport: -99
+ port id: 1,on,PHY,outport: -99
+ port id: 2,on,RING(0),outport: -99
+ port id: 3,on,RING(1),outport: -99
+ }
+
+
+Then, add ``ring 0`` and ``ring 1`` to ``sec 2``.
+
+.. code-block:: console
+
+ spp > sec 2;add ring 0
+ spp > sec 2;add ring 1
+ spp > sec 1;patch 0 2
+ spp > sec 1;patch 3 0
+ spp > sec 2;patch 1 3
+ spp > sec 2;patch 2 1
+ spp > sec 1;forward
+ spp > sec 2;forward
+
+.. code-block:: console
+
+ __
+ ring 0 |
+ +--------+ |
+ +------------+ <--| | | |<-- +-----------+ |
+ | p3| +--------+ |p3 | |
+ | spp_nfv | | spp_nfv | |
+ | (sec 1) p2|--> +--------+ -->|p2 (sec 2) | |
+ +------------+ | | | | +-----------+ |
+ ^ +--------+ ^ |
+ | ring 1 | |
+ v v |
+ +---+----------+--------------------------------------------------+ |
+ | | primary | ^ ^ | |
+ | +----------+ | : | |
+ | : : | |
+ | : | | | host
+ | v v | |
+ | +--------------+ +--------------+ | |
+ | | phy port 0 | | phy port 1 | | |
+ +------------------+--------------+------------+--------------+---+ __|
+ ^ ^
+ | |
+ v v
+
+
+Single spp_nfv with Vhost PMD
+-----------------------------
+
+Vhost PMD
+~~~~~~~~~
+
+Vhost PMD is an interface for communicating between on hsot and guest VM.
+As described in
+:doc:`How to Use<howto_use>`,
+vhost must be created by ``add`` subcommand before the VM is launched.
+
+
+Setup Vhost PMD
+~~~~~~~~~~~~~~~
+
+In this use case, add ``vhost 0`` to ``sec 1`` for communicating
+with the VM.
+First, check if ``/tmp/sock0`` is already exist.
+You have to remove it already exist to avoid failure of socket file
+creation.
+
+.. code-block:: console
+
+ $ ls /tmp | grep sock
+ sock0 ...
+
+ # remove it if exist
+ $ rm /tmp/sock0
+
+Create ``/tmp/sock0`` from ``sec 1``.
+
+.. code-block:: console
+
+ spp > sec 1;add vhost 0
+
+
+Uni-Directional L2fwd with Vhost PMD
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Start a VM with vhost interface as described in
+:doc:`How to Use<howto_use>`
+and launch ``spp_vm`` with secondary ID 2.
+You find ``sec 2`` from controller after launched.
+
+Patch ``port 0`` and ``port 1`` to ``vhost 0`` with ``sec 1``
+running on host.
+Inside VM, configure loopback by patching ``port 0`` and ``port 0``
+with ``sec 2``.
+
+.. code-block:: console
+
+ spp > sec 1;patch 0 2
+ spp > sec 1;patch 2 1
+ spp > sec 2;patch 0 0
+ spp > sec 1;forward
+ spp > sec 2;forward
+
+.. code-block:: console
+
+ __
+ +-----------------------+ |
+ | guest | |
+ | | |
+ | +--------------+ | | guest
+ | | spp_vm | | | 192.168.122.51
+ | | (sec 2) | | |
+ | | p0 | | |
+ +---+--------------+----+ __|
+ ^ :
+ | virtio |
+ | V __
+ +--------------------+ |
+ | spp_nfv | |
+ | p2 (sec 1) | |
+ +--------------------+ |
+ ^ : |
+ | +---------- + |
+ : v |
+ +----+----------+--------------------------------------------+ |
+ | | primary | ^ : | |
+ | +----------+ | : | |
+ | : | | | host
+ | : v | | 192.168.122.1
+ | +--------------+ +--------------+ | |
+ | | phy port 0 | | phy port 1 | | |
+ +------------------+--------------+-------+--------------+---+ __|
+ ^ :
+ | |
+ : v
--
2.7.4
next prev parent reply other threads:[~2018-02-01 4:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-01 4:04 [spp] [PATCH 01/15] docs: add rst docs ogawa.yasufumi
2018-02-01 4:04 ` [spp] [PATCH 02/15] docs: add overview ogawa.yasufumi
2018-02-01 4:04 ` [spp] [PATCH 03/15] docs: add primary commands ogawa.yasufumi
2018-02-01 4:04 ` [spp] [PATCH 04/15] docs: add common commands ogawa.yasufumi
2018-02-01 4:04 ` [spp] [PATCH 05/15] docs: add secondary commands ogawa.yasufumi
2018-02-01 4:04 ` [spp] [PATCH 06/15] docs: add descriptions for pri commands ogawa.yasufumi
2018-02-01 4:04 ` [spp] [PATCH 07/15] docs: fix erata of help command ogawa.yasufumi
2018-02-01 4:04 ` [spp] [PATCH 08/15] docs: revise index in setup chapter ogawa.yasufumi
2018-02-01 4:04 ` [spp] [PATCH 09/15] docs: update getting_started section ogawa.yasufumi
2018-02-01 4:04 ` [spp] [PATCH 10/15] docs: update howto_use section ogawa.yasufumi
2018-02-01 4:04 ` [spp] [PATCH 11/15] docs: add performance_opt section ogawa.yasufumi
2018-02-01 4:04 ` ogawa.yasufumi [this message]
2018-02-01 4:04 ` [spp] [PATCH 13/15] docs: update overview section ogawa.yasufumi
2018-02-01 4:05 ` [spp] [PATCH 14/15] docs: add compile script for rst documentation ogawa.yasufumi
2018-02-01 4:05 ` [spp] [PATCH 15/15] makefile: add target for compile rst documents ogawa.yasufumi
2018-02-05 2:34 ` [spp] [PATCH 01/15] docs: add rst docs Yasufumi Ogawa
2018-02-06 15:22 ` 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=20180201040501.8004-12-ogawa.yasufumi@lab.ntt.co.jp \
--to=ogawa.yasufumi@lab.ntt.co.jp \
--cc=ferruh.yigit@intel.com \
--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).