From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id CFF89A057C for ; Fri, 27 Mar 2020 07:33:55 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 866FB1C028; Fri, 27 Mar 2020 07:33:55 +0100 (CET) Received: from us-smtp-delivery-74.mimecast.com (us-smtp-delivery-74.mimecast.com [63.128.21.74]) by dpdk.org (Postfix) with ESMTP id C6F631BFDE for ; Fri, 27 Mar 2020 07:33:54 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1585290834; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=t02qoLyKR0+OwsgCiFAFJfA/HJS3n70h5ZUiR3lqYkU=; b=f90iuKH7dh8qfnE81vseEUnqDj8oCiCN+ebR+x4FgI10PIAEren15PwRvQOBX5VPefVSaM haggTcdkdyxyqBIgN8sGmnJJXoQTNlqa8ktEs2DTeZh/4BcdQtO1wE6A9BPozvpuF0cLXp E27xK3eIOifux6iC9XqGfe3pWGT1Fm8= Received: from mail-vk1-f200.google.com (mail-vk1-f200.google.com [209.85.221.200]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-28-t53-wdDzPUu7w-QcpSanRw-1; Fri, 27 Mar 2020 02:33:52 -0400 X-MC-Unique: t53-wdDzPUu7w-QcpSanRw-1 Received: by mail-vk1-f200.google.com with SMTP id r141so2220424vke.10 for ; Thu, 26 Mar 2020 23:33:52 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=t02qoLyKR0+OwsgCiFAFJfA/HJS3n70h5ZUiR3lqYkU=; b=D4+ND/jHbY84iVEUqNzlnNFA3yo3c++uJj5D3o1LcYEZ1Gyrhty/vAI4iYQFNxdPk8 6jajgQP/oCTBMJSS4xryVhYuFLHGV7ROnEdkokNJB2mwYexfhzJjXCvdeZtyvsxZziFW J3smaht2oL7v05Y2N3AHs5F5nwCmFOgIlg2D2OWz0upsZFtb4huadBE8KExAX5aQqENr WJK+kfZiyf2pJue3iFFZX7MVTOsONerZ9q31ckN725tUZEQ9TFKhtqixmMzXlKd8bNyZ PvFE4M5eGzt22vNzqNHcO3161is/UoNaixxawvAlTEnM4VtF9vGN1cnHYiZ0QcsbbbAw QXhw== X-Gm-Message-State: ANhLgQ0PEr7cN8siHCn2psI6rgHnjz8jGzwQJ5JtUpNR8Fa2ezhKTz81 txozF98vwMNv2YnPwqNBt40hTGSU+uw87+V3BbzwxkWjhrHOSAbxBVNR93ZF7Z42kZzOa1NOmfZ e6E/3EqJ4dbbNtTnnUiFzOaE= X-Received: by 2002:a1f:5f53:: with SMTP id t80mr9802527vkb.39.1585290832108; Thu, 26 Mar 2020 23:33:52 -0700 (PDT) X-Google-Smtp-Source: ADFU+vtPu74eGycGXOF+ONyDPP8VwiuVkUFVT/fwmjDIt851g+XosGSi0YvWbOxXjVH8J/rfVyhgm/X185NExrJpXeg= X-Received: by 2002:a1f:5f53:: with SMTP id t80mr9802508vkb.39.1585290831324; Thu, 26 Mar 2020 23:33:51 -0700 (PDT) MIME-Version: 1.0 References: <99d72c1b91e3fce36713b529ab47e8aa3fd78454.1579885526.git.anatoly.burakov@intel.com> <5ebcce5b7df8fa0620b3d0fd6bf67a0668b942ac.1581073866.git.anatoly.burakov@intel.com> In-Reply-To: From: David Marchand Date: Fri, 27 Mar 2020 07:33:40 +0100 Message-ID: To: "Burakov, Anatoly" Cc: dev , dpdk stable X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Subject: Re: [dpdk-stable] [PATCH v3] eal/mem: preallocate VA space in no-huge mode X-BeenThere: stable@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches for DPDK stable branches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: stable-bounces@dpdk.org Sender: "stable" On Thu, Mar 26, 2020 at 6:07 PM Burakov, Anatoly wrote: > > On 25-Mar-20 2:39 PM, David Marchand wrote: > > On Fri, Feb 7, 2020 at 12:11 PM Anatoly Burakov > > wrote: > >> > >> When --no-huge mode is used, the memory is currently allocated with > >> mmap(NULL, ...). This is fine in most cases, but can fail in cases > >> where DPDK is run on a machine with an IOMMU that is of more limited > >> address width than that of a VA, because we're not specifying the > >> address hint for mmap() call. > >> > >> Fix it by preallocating VA space before mapping it. > >> > >> Cc: stable@dpdk.org > >> > >> Signed-off-by: Anatoly Burakov > > > > Reproduced issue reported by Thomas on v2. > > Works fine with v3. > > > > Tested-by: David Marchand > > > > > > Does this issue affect FreeBSD too? > > > > I don't think we have support for IOMMU on FreeBSD so my guess is no :) Fair enough, I will take it today. Thanks. -- David Marchand