From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [dpdk-stable] [PATCH v3 1/2] memalloc: do not leave unmapped holes in EAL virtual memory area Date: Thu, 12 Jul 2018 23:42:19 +0200 Message-ID: <3545756.MiBi3UpLtl@xps> References: <1527860361-162114-1-git-send-email-dariuszx.stojaczyk@intel.com> <1527857960-109306-1-git-send-email-dariuszx.stojaczyk@intel.com> <5ab83fb6-47d0-d8ca-9efe-b6ac93f3217f@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: stable@dpdk.org, "Burakov, Anatoly" , dev@dpdk.org To: Dariusz Stojaczyk Return-path: In-Reply-To: <5ab83fb6-47d0-d8ca-9efe-b6ac93f3217f@intel.com> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 01/06/2018 17:06, Burakov, Anatoly: > On 01-Jun-18 1:59 PM, Dariusz Stojaczyk wrote: > > EAL reserves a huge area in virtual address space > > to provide virtual address contiguity for e.g. > > future memory extensions (memory hotplug). During > > memory hotplug, if the hugepage mmap succeeds but > > doesn't suffice EAL's requiriments, the EAL would > > unmap this mapping straight away, leaving a hole in > > its virtual memory area and making it available > > to everyone. As EAL still thinks it owns the entire > > region, it may try to mmap it later with MAP_FIXED, > > possibly overriding a user's mapping that was made > > in the meantime. > > > > This patch ensures each hole is mapped back by EAL, > > so that it won't be available to anyone else. > > > > Changes from v2: > > * replaced rte_panic() with a CRIT log. > > * added "git fixline" tags > > > > Changes from v1: > > * checkpatch fixes > > > > Fixes: 582bed1e1d1d ("mem: support mapping hugepages at runtime") > > Cc: anatoly.burakov@intel.com > > Cc: stable@dpdk.org > > > > Signed-off-by: Dariusz Stojaczyk > > --- > > Acked-by: Anatoly Burakov > > Thomas, could you please fix the commit message on apply? Yes Applied, thanks