From: Chas Williams <3chas3@gmail.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: dev@dpdk.org, anatoly.burakov@intel.com, 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:23:41 -0500 [thread overview]
Message-ID: <CAG2-GkkSkuZj3Cy7kxunP4a5hY61XK5MHPz_t8Tjjfz4rRzeNg@mail.gmail.com> (raw)
In-Reply-To: <2600590.OO5gESNU7Y@xps>
The particular machine in my case is a Dell Optiplex 790 which is fairly
similar to another system that has basically the same problem. The IOMMU
advertises that is can only handle 39 bits of addressing. The DMAR address
tables have a width of 36 bits, so all is well when using IOVA physical
addresses. With IOVA virtual addresses, they sometimes go beyond the 39
bit boundary. I was under the impression that IOMMU widths are more
typically 48 bits, but I appear to have some low end systems with a simpler
IOMMU.
I could make it a runtime option.
On Thu, Nov 30, 2017 at 4:17 AM, Thomas Monjalon <thomas@monjalon.net>
wrote:
> 30/11/2017 03:57, Chas Williams:
> > 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.
>
> Which machines are you talking about?
> A run-time option may be a better solution.
>
>
next prev parent reply other threads:[~2017-12-03 0:23 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 [this message]
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
-- 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-GkkSkuZj3Cy7kxunP4a5hY61XK5MHPz_t8Tjjfz4rRzeNg@mail.gmail.com \
--to=3chas3@gmail.com \
--cc=anatoly.burakov@intel.com \
--cc=chas3@att.com \
--cc=dev@dpdk.org \
--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).