From: Chas Williams <3chas3@gmail.com>
To: Hemant Agrawal <hemant.agrawal@nxp.com>
Cc: dev@dpdk.org, anatoly.burakov@intel.com,
Thomas Monjalon <thomas@monjalon.net>,
Chas Williams <chas3@att.com>
Subject: Re: [dpdk-dev] [PATCH] eal: add option to force IOVA as PA mode
Date: Sat, 2 Dec 2017 19:25:06 -0500 [thread overview]
Message-ID: <CAG2-GkmR7e3ga11twVcCKMrY3YEFYVLksyksny7dgcV7+ofy4Q@mail.gmail.com> (raw)
In-Reply-To: <5c919800-d135-6cac-1385-d1d0c58808d8@nxp.com>
On Fri, Dec 1, 2017 at 12:48 AM, Hemant Agrawal <hemant.agrawal@nxp.com>
wrote:
> On 11/30/2017 8:27 AM, Chas Williams wrote:
>
>> From: Chas Williams <chas3@att.com>
>>
>> The IOMMU in some machines report that they can only support
>> limited widths. IOVA virtual addresses may exceed this width
>> making the use of IOVA virtual addresses difficult. The option
>> CONFIG_RTE_LIBRTE_USE_PHYS_IOVA can used to force IOVA physical
>> address usage.
>>
>>
> Is it possible to dynamically detect the machine limitation in bus iova
> code instead of compile time option?
>
>
Yes, I think you can examine the "cap" of the IOMMU group in /sys and
determine the bit width. I will have to check on that.
next prev parent reply other threads:[~2017-12-03 0:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-30 2:57 Chas Williams
2017-11-30 9:17 ` Thomas Monjalon
2017-12-03 0:23 ` Chas Williams
2018-01-12 0:12 ` Thomas Monjalon
2018-01-12 3:28 ` Chas Williams
2017-12-01 5:48 ` Hemant Agrawal
2017-12-03 0:25 ` Chas Williams [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-11-30 2:57 Chas Williams
2017-11-30 2:56 Chas Williams
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=CAG2-GkmR7e3ga11twVcCKMrY3YEFYVLksyksny7dgcV7+ofy4Q@mail.gmail.com \
--to=3chas3@gmail.com \
--cc=anatoly.burakov@intel.com \
--cc=chas3@att.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=thomas@monjalon.net \
/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).