From mboxrd@z Thu Jan 1 00:00:00 1970 From: Olivier Matz Subject: Re: [PATCH v3 00/35] mempool: rework memory allocation Date: Mon, 13 Jun 2016 12:27:43 +0200 Message-ID: <575E8A9F.8080402@6wind.com> References: <1460629199-32489-1-git-send-email-olivier.matz@6wind.com> <36612895.rbhkJEDisP@xps13> <9d61a426-f580-b39e-1e38-7a30a4937324@redhat.com> <2024350.zjYMIZz45a@xps13> <5742B4A0.7030309@6wind.com> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Cc: dev@dpdk.org To: Thomas Monjalon , Panu Matilainen Return-path: Received: from mail.droids-corp.org (zoll.droids-corp.org [94.23.50.67]) by dpdk.org (Postfix) with ESMTP id A0A365594 for ; Mon, 13 Jun 2016 12:27:49 +0200 (CEST) In-Reply-To: <5742B4A0.7030309@6wind.com> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Hi, On 05/23/2016 09:43 AM, Olivier Matz wrote: > Hi Panu, Thomas, > > On 05/20/2016 11:09 AM, Thomas Monjalon wrote: >> 2016-05-20 11:42, Panu Matilainen: >>> Just noticed this series "breaks" --no-huge as a regular user, commit >>> 593a084afc2b to be exact: >>> >>> mmap(NULL, 4194304, PROT_READ|PROT_WRITE, >>> MAP_PRIVATE|MAP_ANONYMOUS|MAP_LOCKED, 0, 0) = -1 EAGAIN (Resource >>> temporarily unavailable) >>> write(1, "EAL: rte_eal_hugepage_init: mmap"..., 76EAL: >>> rte_eal_hugepage_init: mmap() failed: Resource temporarily unavailable >>> >>> "Breaks" in quotes because I guess it always was broken (as the >>> non-locked pages might not be in physical memory) and because its >>> possible to adjust resourse limits to allow the operation to succeed. >>> If you're root, that is. >>> >>> I was just looking into making the test-suite runnable by a regular user >>> with no special privileges, >> >> I have the same dream, to make sure every developer can run the unit tests >> easily and quickly. > > Thanks Panu for the feedback on this, I didn't notice this regression > for a regular user. > > The goal of this commit was to do a step forward in the direction > of a working --no-huge: locking the pages in physical memory is > mandatory for most physical drivers. But as described at the end > of http://dpdk.org/ml/archives/dev/2016-May/039229.html , the > --no-huge option is still not working because the physical addresses > are not correct. > > So I think it wouldn't be a problem to revert this commit if it breaks > something. I've just sent a patch to fix that. Feel free to comment. See http://www.dpdk.org/ml/archives/dev/2016-June/041051.html Regards, Olivier