From: ogawa.yasufumi@lab.ntt.co.jp
To: ferruh.yigit@intel.com, spp@dpdk.org, ogawa.yasufumi@lab.ntt.co.jp
Subject: [spp] [PATCH 08/11] docs: add spp_primary in design section
Date: Wed, 9 Jan 2019 10:49:29 +0900 [thread overview]
Message-ID: <1546998573-26108-9-git-send-email-ogawa.yasufumi@lab.ntt.co.jp> (raw)
In-Reply-To: <1546998573-26108-1-git-send-email-ogawa.yasufumi@lab.ntt.co.jp>
From: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
Add descriptions for design of spp_primary.
Signed-off-by: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
---
docs/guides/overview/design.rst | 23 +++++++++++++++++++++++
1 file changed, 23 insertions(+)
diff --git a/docs/guides/overview/design.rst b/docs/guides/overview/design.rst
index 8a7f6b7..7706488 100644
--- a/docs/guides/overview/design.rst
+++ b/docs/guides/overview/design.rst
@@ -92,6 +92,29 @@ SPP CLI is able to communicate several ``spp-ctl`` to support multiple nodes
configuration.
+.. _spp_overview_design_spp_primary:
+
+SPP Primary
+-----------
+
+SPP is originally derived from
+`Client-Server Multi-process Example
+<https://doc.dpdk.org/guides/sample_app_ug/multi_process.html#client-server-multi-process-example>`_
+of
+`Multi-process Sample Application
+<https://doc.dpdk.org/guides/sample_app_ug/multi_process.html>`_
+in DPDK's sample applications.
+``spp_primary`` is a server process for other secondary processes and
+basically working as described in
+"How the Application Works" section of the sample application.
+
+However, there are also differences between ``spp_primary`` and
+the server process of the sample application.
+``spp_primary`` has no limitation of the number of secondary processes.
+It does not work for packet forwaring, but just provide rings and memory pools
+for secondary processes.
+
+
Reference
---------
--
2.7.4
next prev parent reply other threads:[~2019-01-09 1:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-09 1:49 [spp] Update docs structure ogawa.yasufumi
2019-01-09 1:49 ` [spp] [PATCH 01/11] docs: change structure of overview section ogawa.yasufumi
2019-01-09 1:49 ` [spp] [PATCH 02/11] docs: move overview of spp-ctl to SPP overview ogawa.yasufumi
2019-01-09 1:49 ` [spp] [PATCH 03/11] docs: update image of " ogawa.yasufumi
2019-01-09 1:49 ` [spp] [PATCH 04/11] docs: update overview section ogawa.yasufumi
2019-01-09 1:49 ` [spp] [PATCH 05/11] docs: add overview image for design section ogawa.yasufumi
2019-01-09 1:49 ` [spp] [PATCH 06/11] docs: add image of design of spp-ctl ogawa.yasufumi
2019-01-09 1:49 ` [spp] [PATCH 07/11] docs: add SPP controller in design section ogawa.yasufumi
2019-01-09 1:49 ` ogawa.yasufumi [this message]
2019-01-09 1:49 ` [spp] [PATCH 09/11] docs: move design section to doc root ogawa.yasufumi
2019-01-09 1:49 ` [spp] [PATCH 10/11] docs: move usecases " ogawa.yasufumi
2019-01-09 1:49 ` [spp] [PATCH 11/11] docs: remove spp-ctl section 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=1546998573-26108-9-git-send-email-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).