DPDK patches and discussions
 help / color / mirror / Atom feed
From: eric zhang <eric.zhang@windriver.com>
To: <anatoly.burakov@intel.com>, <john.mcnamara@intel.com>
Cc: <allain.legacy@windriver.com>, <matt.peters@windriver.com>,
	<dev@dpdk.org>
Subject: [dpdk-dev] [PATCH v3 3/3] doc: document --iova-mode EAL option
Date: Wed, 3 Oct 2018 16:53:14 -0400	[thread overview]
Message-ID: <1538599994-23331-4-git-send-email-eric.zhang@windriver.com> (raw)
In-Reply-To: <1538599994-23331-1-git-send-email-eric.zhang@windriver.com>

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 34d871c..208c454 100644
--- a/doc/guides/prog_guide/env_abstraction_layer.rst
+++ b/doc/guides/prog_guide/env_abstraction_layer.rst
@@ -225,6 +225,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 bus and IOMMU configuration, may not report
+the desired addressing mode when virtual devices that are not directly attached to the bus are present.
+To facilitate forcing the IOVA mode to a specific value the EAL command line option ``--iova-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 4c0d2ce..94fd0cc 100644
--- a/doc/guides/testpmd_app_ug/run_app.rst
+++ b/doc/guides/testpmd_app_ug/run_app.rst
@@ -156,6 +156,10 @@ See the DPDK Getting Started Guides for more information on these options.
 
     Use malloc instead of hugetlbfs.
 
+*   ``--iova-mode <pa|va>``
+
+    Force IOVA mode to a specific value.
+
 
 Testpmd Command-line Options
 ----------------------------
-- 
1.8.3.1

  parent reply	other threads:[~2018-10-03 20:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-03 20:53 [dpdk-dev] [PATCH v3 0/3] force IOVA to a particular mode eric zhang
2018-10-03 20:53 ` [dpdk-dev] [PATCH v3 1/3] eal: add eal option to configure iova mode eric zhang
2018-10-03 20:53 ` [dpdk-dev] [PATCH v3 2/3] eal: force IOVA to a particular mode eric zhang
2018-10-03 20:53 ` eric zhang [this message]
2018-10-18 13:18   ` [dpdk-dev] [PATCH v3 3/3] doc: document --iova-mode EAL option Kovacevic, Marko
2018-10-04  9:19 ` [dpdk-dev] [PATCH v3 0/3] force IOVA to a particular mode Burakov, Anatoly
2018-10-11 10:08   ` Thomas Monjalon
2018-10-28 23:04     ` Thomas Monjalon
2018-10-30 12:02       ` Alejandro Lucero
2018-10-30 13:47         ` Burakov, Anatoly
2018-10-30 14:03           ` Alejandro Lucero

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=1538599994-23331-4-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=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).