From: Yasufumi Ogawa <yasufum.o@gmail.com>
To: spp@dpdk.org, ferruh.yigit@intel.com, yasufum.o@gmail.com
Subject: [spp] [PATCH 3/3] docs: add usage of blacklist for SPP container
Date: Mon, 12 Aug 2019 16:13:09 +0900 [thread overview]
Message-ID: <20190812071309.18991-4-yasufum.o@gmail.com> (raw)
In-Reply-To: <20190812071309.18991-1-yasufum.o@gmail.com>
This update is to add description of usage of blacklist option. It
describes how to inspect PCI addresses and how to specify them while
launching app container.
Signed-off-by: Yasufumi Ogawa <yasufum.o@gmail.com>
---
docs/guides/tools/sppc/getting_started.rst | 45 +++++++++++++++++++++-
1 file changed, 44 insertions(+), 1 deletion(-)
diff --git a/docs/guides/tools/sppc/getting_started.rst b/docs/guides/tools/sppc/getting_started.rst
index d92b55f..4834cc0 100644
--- a/docs/guides/tools/sppc/getting_started.rst
+++ b/docs/guides/tools/sppc/getting_started.rst
@@ -256,9 +256,52 @@ app container launcher.
Done
testpmd>
-
It launches ``testpmd`` in foreground mode.
+.. note::
+
+ DPDK app container tries to own ports on host which are shared with host
+ and containers by default. It causes a confliction between SPP running on
+ host and containers and unexpected behavior.
+
+ To avoid this situation, it is required to use ``-b`` or
+ ``--pci-blacklist`` EAL option to exclude ports on host. PCI address of
+ port can be inspected by using ``dpdk-devbind.py -s``.
+
+If you have ports on host and assign them to SPP, you should to exclude them
+from the app container by specifying PCI addresses of the ports with ``-b``
+or ``--pci-blacklist``.
+
+You can find PCI addresses from ``dpdk-devbind.py -s``.
+
+.. code-block:: console
+
+ # Check the status of the available devices.
+ dpdk-devbind --status
+ Network devices using DPDK-compatible driver
+ ============================================
+ 0000:0a:00.0 '82599ES 10-Gigabit' drv=igb_uio unused=ixgbe
+ 0000:0a:00.1 '82599ES 10-Gigabit' drv=igb_uio unused=ixgbe
+
+ Network devices using kernel driver
+ ===================================
+ ...
+
+In this case, you should exclude ``0000:0a:00.0`` and ``0000:0a:00.1``
+with ``-b`` option.
+
+.. code-block:: console
+
+ # Terminal 3
+ $ cd /path/to/spp/tools/sppc
+ $ app/testpmd.py -l 3-4 -d 1,2 \
+ -b 0000:0a:00.0 0000:0a:00.1
+ sudo docker run -it \
+ ...
+ -b 0000:0a:00.0 \
+ -b 0000:0a:00.1 \
+ ...
+
.. _sppc_gs_run_apps:
--
2.17.1
prev parent reply other threads:[~2019-08-12 7:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-12 7:13 [spp] [PATCH 0/3] Add blacklist EAL option " Yasufumi Ogawa
2019-08-12 7:13 ` [spp] [PATCH 1/3] tools/sppc: add blacklist and whitelist options Yasufumi Ogawa
2019-08-12 7:13 ` [spp] [PATCH 2/3] docs: add two optiosn to examples of sppc Yasufumi Ogawa
2019-08-12 7:13 ` 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=20190812071309.18991-4-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).