From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm0-f48.google.com (mail-wm0-f48.google.com [74.125.82.48]) by dpdk.org (Postfix) with ESMTP id 5A178ADD8 for ; Fri, 20 May 2016 11:09:10 +0200 (CEST) Received: by mail-wm0-f48.google.com with SMTP id n129so262770068wmn.1 for ; Fri, 20 May 2016 02:09:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=6wind-com.20150623.gappssmtp.com; s=20150623; h=from:to:cc:subject:date:message-id:user-agent:in-reply-to :references:mime-version:content-transfer-encoding; bh=uJi3sx6Ym46UV/EWY3vIaHx90nDySC7JQkYveIV7Us4=; b=m0hwfg3eDsbchAv3uic9C3uOVnnaKYd7exU24/XrhY+7MlYGZVPF2UNbHSVogX1apZ B1QvX2IEOqzmKyMYloDWX3XHwhrfg/BJXbyOmQSKEVgfhEoTQslS9mlsAXJM8rAQxS/F tTgsoNHrVHEs0oLWrGVTcb7p0lH0W9gL4gnZ1j8kqNjErLlyzJ5DKn7CvMmRdO4YeT34 HxqkUqCOgoY5Onv2wQ1KdvD3BfpcuaWxj0cqmcgs/LX55JrkImobGps8cJPoVYcHpWCS cx79+2Yb1/m3IoMWBDUYwvRVRy/hawmyCrZq6GcoNgHd2r4cej6EkczSh7B9qLw4/Ef7 mlWg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:date:message-id:user-agent :in-reply-to:references:mime-version:content-transfer-encoding; bh=uJi3sx6Ym46UV/EWY3vIaHx90nDySC7JQkYveIV7Us4=; b=jSNciLc0SwDTfTgOdhQuGrAFwtVP0RZATL9DxHuwSEMS8TrCxGvAtc7G64gjbseo/U zM3TT8U5s9V22IemvjvqHK7N/GmTOQaFbWhIuCzvxiGt+bae+aqjrZouBKt9oSxluuPV Nr6x8rrg/hP3RrNatI/NSGH0GrlJ8HeeR/BzzaWU/k3z08je3mAgPGPiJ7VVhIXHwVCF xPMqxgb4doHig3ng7SUse13AMFJkR/TD8LtNxPAH4KMzMsvsHQH0GNjcZjCQCvIXBbAO OZ1hDf96ubM5OxwZyftdQOJNfnjYhkqpdhwnZr4qDeW1hmSruHOSTV2Y3hXcmrhxVY39 qiFA== X-Gm-Message-State: AOPr4FUk5+DQUMZ8ey7sI6DUMsjuzCJ6z3G2G/QQNEDumPauvdqyF+MIkdVpebCElU4zPGSH X-Received: by 10.28.194.69 with SMTP id s66mr2573232wmf.88.1463735350079; Fri, 20 May 2016 02:09:10 -0700 (PDT) Received: from xps13.localnet (184.203.134.77.rev.sfr.net. [77.134.203.184]) by smtp.gmail.com with ESMTPSA id t78sm1827593wmt.3.2016.05.20.02.09.09 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 20 May 2016 02:09:09 -0700 (PDT) From: Thomas Monjalon To: Panu Matilainen Cc: Olivier Matz , dev@dpdk.org Date: Fri, 20 May 2016 11:09:08 +0200 Message-ID: <2024350.zjYMIZz45a@xps13> User-Agent: KMail/4.14.10 (Linux/4.1.6-1-ARCH; KDE/4.14.11; x86_64; ; ) In-Reply-To: <9d61a426-f580-b39e-1e38-7a30a4937324@redhat.com> References: <1460629199-32489-1-git-send-email-olivier.matz@6wind.com> <36612895.rbhkJEDisP@xps13> <9d61a426-f580-b39e-1e38-7a30a4937324@redhat.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v3 00/35] mempool: rework memory allocation X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 May 2016 09:09:10 -0000 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. > primarily to make it possible to run the > testsuite as part of rpm package builds (in %check), and no special > setup or extra privileges can be assumed there. Such tests are of course > of limited coverage but still better than nothing, and --no-huge was my > ticket there. Talk about bad timing :) > > It'd be fine to have limited subset of tests to run when non-privileged > but since this one lives inside rte_eal_init() it practically prevents > everything, unless I'm missing some other magic switch or such. Thoughts? This change was done for mbuf allocation because they are passed to the hardware. We should not have any hardware constraint in the unit tests. So I'd say it is a requirement for the memory rework. We must be capable to allocate some locked pages if required, and some standard pages for other usages. Please jump in this thread: http://dpdk.org/ml/archives/dev/2016-April/037444.html