From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: eric zhang <eric.zhang@windriver.com>, john.mcnamara@intel.com
Cc: allain.legacy@windriver.com, matt.peters@windriver.com, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v3 0/3] force IOVA to a particular mode
Date: Thu, 4 Oct 2018 10:19:07 +0100 [thread overview]
Message-ID: <f61b476a-1a92-bffc-fe72-09af3f05e015@intel.com> (raw)
In-Reply-To: <1538599994-23331-1-git-send-email-eric.zhang@windriver.com>
On 03-Oct-18 9:53 PM, eric zhang wrote:
> This patchset introduces an EAL command line option "--iova-mode"
> to give the user a facility to force IOVA mode to a special value.
>
> 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.
> The EAL command line option "--iova-mode" can be used to select either
> physical addressing('pa') or virtual addressing('va').
>
> ------
> v3:
> * document --iova-mode EAL option
> * change default iova mode to RTE_IOVA_DC
>
> v2:
> * use eal option instead of compilation option to configure IOVA
> * apply http://patchwork.dpdk.org/patch/25192/
>
>
> Santosh Shukla (1):
> eal: add eal option to configure iova mode
>
> eric zhang (2):
> eal: force IOVA to particular mode
> doc:document --iova-mode EAL flag
>
> doc/guides/prog_guide/env_abstraction_layer.rst | 8 +++++++
> doc/guides/testpmd_app_ug/run_app.rst | 4 ++++
> lib/librte_eal/bsdapp/eal/eal.c | 11 +++++++--
> lib/librte_eal/common/eal_common_options.c | 30 +++++++++++++++++++++++++
> lib/librte_eal/common/eal_internal_cfg.h | 1 +
> lib/librte_eal/common/eal_options.h | 2 ++
> lib/librte_eal/linuxapp/eal/eal.c | 27 +++++++++++++---------
> 7 files changed, 71 insertions(+), 12 deletions(-)
>
Acked-by: Anatoly Burakov <anatoly.burakov@intel.com>
--
Thanks,
Anatoly
next prev parent reply other threads:[~2018-10-04 9:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-03 20:53 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 ` [dpdk-dev] [PATCH v3 3/3] doc: document --iova-mode EAL option eric zhang
2018-10-18 13:18 ` Kovacevic, Marko
2018-10-04 9:19 ` Burakov, Anatoly [this message]
2018-10-11 10:08 ` [dpdk-dev] [PATCH v3 0/3] force IOVA to a particular mode 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=f61b476a-1a92-bffc-fe72-09af3f05e015@intel.com \
--to=anatoly.burakov@intel.com \
--cc=allain.legacy@windriver.com \
--cc=dev@dpdk.org \
--cc=eric.zhang@windriver.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).