From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH] eal: add option to force IOVA as PA mode Date: Fri, 12 Jan 2018 01:12:36 +0100 Message-ID: <1773541.G656isd0hF@xps> References: <20171130025739.4349-1-3chas3@gmail.com> <2600590.OO5gESNU7Y@xps> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org, anatoly.burakov@intel.com To: Chas Williams <3chas3@gmail.com>, Chas Williams Return-path: Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by dpdk.org (Postfix) with ESMTP id 5C38671B4 for ; Fri, 12 Jan 2018 01:13:05 +0100 (CET) In-Reply-To: List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 03/12/2017 01:23, Chas Williams: > 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 > wrote: > > > 30/11/2017 03:57, Chas Williams: > > > From: Chas Williams > > > > > > 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. Please check the patch from Maxime: https://dpdk.org/dev/patchwork/patch/33192/