From: Yasufumi Ogawa <yasufum.o@gmail.com>
To: spp@dpdk.org, ferruh.yigit@intel.com, yasufum.o@gmail.com
Subject: [spp] [PATCH 2/2] docs: add single file segments EAL option for sppc
Date: Thu, 15 Aug 2019 17:03:39 +0900 [thread overview]
Message-ID: <20190815080339.27914-3-yasufum.o@gmail.com> (raw)
In-Reply-To: <20190815080339.27914-1-yasufum.o@gmail.com>
This update is to add examples of `blacklist` and `whitelist` to
examples of SPP container tools.
Signed-off-by: Yasufumi Ogawa <yasufum.o@gmail.com>
---
docs/guides/tools/sppc/app_launcher.rst | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/docs/guides/tools/sppc/app_launcher.rst b/docs/guides/tools/sppc/app_launcher.rst
index 80dc262..009bc80 100644
--- a/docs/guides/tools/sppc/app_launcher.rst
+++ b/docs/guides/tools/sppc/app_launcher.rst
@@ -144,6 +144,7 @@ On the other hand, application specific options are different each other.
[--socket-mem SOCKET_MEM]
[-b [PCI_BLACKLIST [PCI_BLACKLIST ...]]]
[-w [PCI_WHITELIST [PCI_WHITELIST ...]]]
+ [--single-file-segment]
[--nof-memchan NOF_MEMCHAN] [-n NOF_RING]
[-p PORT_MASK]
[-dv DEV_VHOST_IDS] [-dt DEV_TAP_IDS] [-ip CTRL_IP]
@@ -166,6 +167,9 @@ On the other hand, application specific options are different each other.
PCI blacklist for excluding devices
-w [PCI_WHITELIST [PCI_WHITELIST ...]], --pci-whitelist [PCI_WHITELIST..
PCI whitelist for including devices
+ --single-file-segments
+ Create fewer files in hugetlbfs (non-legacy mode
+ only).
--nof-memchan NOF_MEMCHAN
Number of memory channels (default is 4)
-n NOF_RING, --nof-ring NOF_RING
@@ -218,6 +222,7 @@ It shows only application specific options for simplicity.
[--socket-mem SOCKET_MEM] [--nof-memchan NOF_MEMCHAN]
[-b [PCI_BLACKLIST [PCI_BLACKLIST ...]]]
[-w [PCI_WHITELIST [PCI_WHITELIST ...]]]
+ [--single-file-segment]
[-i SEC_ID] [-ip CTRL_IP] [--ctrl-port CTRL_PORT]
[--dist-name DIST_NAME] [--dist-ver DIST_VER]
[-ci CONTAINER_IMAGE] [-fg] [--dry-run]
@@ -268,6 +273,7 @@ It shows options without of EAL and container for simplicity.
usage: l2fwd.py [-h] [-l CORE_LIST] [-c CORE_MASK] [-m MEM]
[--socket-mem SOCKET_MEM] [--nof-memchan NOF_MEMCHAN]
[-b [PCI_BLACKLIST [PCI_BLACKLIST ...]]]
+ [--single-file-segment]
[-w [PCI_WHITELIST [PCI_WHITELIST ...]]]
[-d DEV_IDS] [-nq NOF_QUEUES] [--no-privileged]
[-p PORT_MASK]
@@ -386,6 +392,7 @@ It shows options without of EAL and container for simplicity.
[--socket-mem SOCKET_MEM] [--nof-memchan NOF_MEMCHAN]
[-b [PCI_BLACKLIST [PCI_BLACKLIST ...]]]
[-w [PCI_WHITELIST [PCI_WHITELIST ...]]]
+ [--single-file-segment]
[-d DEV_IDS] [-nq NOF_QUEUES] [--no-privileged]
[-p PORT_MASK] [--config CONFIG] [-P] [-E] [-L]
[-dst [ETH_DEST [ETH_DEST ...]]] [--enable-jumbo]
@@ -485,6 +492,7 @@ It shows options without of EAL and container.
[--socket-mem SOCKET_MEM] [--nof-memchan NOF_MEMCHAN]
[-b [PCI_BLACKLIST [PCI_BLACKLIST ...]]]
[-w [PCI_WHITELIST [PCI_WHITELIST ...]]]
+ [--single-file-segment]
[-d DEV_IDS] [-nq NOF_QUEUES] [--no-privileged]
[--pci] [-i] [-a] [--tx-first]
[--stats-period STATS_PERIOD]
@@ -770,6 +778,7 @@ It shows options without of EAL and container for simplicity.
[--socket-mem SOCKET_MEM] [--nof-memchan NOF_MEMCHAN]
[-b [PCI_BLACKLIST [PCI_BLACKLIST ...]]]
[-w [PCI_WHITELIST [PCI_WHITELIST ...]]]
+ [--single-file-segment]
[-d DEV_IDS] [-nq NOF_QUEUES] [--no-privileged]
[--matrix MATRIX] [--log-level LOG_LEVEL]
[--dist-name DIST_NAME] [--dist-ver DIST_VER]
@@ -978,6 +987,7 @@ Refer options and usages by ``load-balancer.py -h``.
[--socket-mem SOCKET_MEM]
[-b [PCI_BLACKLIST [PCI_BLACKLIST ...]]]
[-w [PCI_WHITELIST [PCI_WHITELIST ...]]]
+ [--single-file-segment]
[--nof-memchan NOF_MEMCHAN]
[-d DEV_IDS] [-nq NOF_QUEUES] [--no-privileged]
[-rx RX_PORTS] [-tx TX_PORTS] [-w WORKER_LCORES]
--
2.17.1
prev parent reply other threads:[~2019-08-15 8:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-15 8:03 [spp] [PATCH 0/2] Add --single-file-segments option to SPP container Yasufumi Ogawa
2019-08-15 8:03 ` [spp] [PATCH 1/2] tools/sppc: add single file segments EAL option Yasufumi Ogawa
2019-08-16 9:12 ` [spp] PDF document compilation on CentOS Hideyuki Yamashita
2019-08-17 6:10 ` Yasufumi Ogawa
2019-08-19 1:24 ` 中村宏之
2019-08-15 8:03 ` Yasufumi Ogawa [this message]
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=20190815080339.27914-3-yasufum.o@gmail.com \
--to=yasufum.o@gmail.com \
--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).