From: eric zhang <eric.zhang@windriver.com>
To: <john.mcnamara@intel.com>, <anatoly.burakov@intel.com>,
<hemant.agrawal@nxp.com>
Cc: <allain.legacy@windriver.com>, <matt.peters@windriver.com>,
<dev@dpdk.org>
Subject: [dpdk-dev] [PATCH] doc: update the doc for adding EAL option
Date: Mon, 1 Oct 2018 11:54:50 -0400 [thread overview]
Message-ID: <1538409290-24998-1-git-send-email-eric.zhang@windriver.com> (raw)
This patch updates Programmer's Guide and EAL parameter guides
to show EAL option "--iova-mode" support.
Signed-off-by: eric zhang <eric.zhang@windriver.com>
---
doc/guides/prog_guide/env_abstraction_layer.rst | 8 ++++++++
doc/guides/testpmd_app_ug/run_app.rst | 4 ++++
2 files changed, 12 insertions(+)
diff --git a/doc/guides/prog_guide/env_abstraction_layer.rst b/doc/guides/prog_guide/env_abstraction_layer.rst
index d362c92..a47fb38 100644
--- a/doc/guides/prog_guide/env_abstraction_layer.rst
+++ b/doc/guides/prog_guide/env_abstraction_layer.rst
@@ -321,6 +321,14 @@ Misc Functions
Locks and atomic operations are per-architecture (i686 and x86_64).
+IOVA Mode Configuration
+~~~~~~~~~~~~~~~~~~~~~~~
+
+Auto detection of the IOVA mode, based on probing the PCI bus and IOMMU configuration, may not report
+the desired addressing mode when virtual devices that are not directly attached to the PCI bus are present.
+To facilitate forcing the IOVA mode to a specific value the EAL command line option ``--iova-mode=mode`` can
+be used to select either physical addressing('pa') or virtual addressing('va').
+
Memory Segments and Memory Zones (memzone)
------------------------------------------
diff --git a/doc/guides/testpmd_app_ug/run_app.rst b/doc/guides/testpmd_app_ug/run_app.rst
index f301c2b..be2911c 100644
--- a/doc/guides/testpmd_app_ug/run_app.rst
+++ b/doc/guides/testpmd_app_ug/run_app.rst
@@ -133,6 +133,10 @@ See the DPDK Getting Started Guides for more information on these options.
Use malloc instead of hugetlbfs.
+* ``--iova-mode=mode``
+
+ Force IOVA mode to a specific value. Valid values are 'pa' or 'va'.
+
Testpmd Command-line Options
----------------------------
--
2.7.4
next reply other threads:[~2018-10-01 15:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-01 15:54 eric zhang [this message]
2018-10-02 9:59 ` Burakov, Anatoly
2018-10-02 10:04 ` Thomas Monjalon
2018-10-02 12:58 ` Ferruh Yigit
2018-10-02 20:05 ` Eric Zhang
2018-10-03 10:53 ` Burakov, Anatoly
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=1538409290-24998-1-git-send-email-eric.zhang@windriver.com \
--to=eric.zhang@windriver.com \
--cc=allain.legacy@windriver.com \
--cc=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=john.mcnamara@intel.com \
--cc=matt.peters@windriver.com \
/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).