From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH v8] eal: map PCI memory resources after hugepages Date: Tue, 25 Nov 2014 18:17:46 +0100 Message-ID: <2634610.dyaITUHquj@xps13> References: <1415619272-8281-1-git-send-email-anatoly.burakov@intel.com> <1415700565-19157-1-git-send-email-anatoly.burakov@intel.com> <20141113134655.GA8224@bricha3-MOBL3> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev-VfR2kkLFssw@public.gmane.org To: Anatoly Burakov Return-path: In-Reply-To: <20141113134655.GA8224@bricha3-MOBL3> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces-VfR2kkLFssw@public.gmane.org Sender: "dev" > > Multi-process DPDK application must mmap hugepages and PCI resources > > into the same virtual address space. By default the virtual addresses > > are chosen by the primary process automatically when calling the mmap. > > But sometimes the chosen virtual addresses aren't usable in secondary > > process - for example, secondary process is linked with more libraries > > than primary process, and the library occupies the same address space > > that the primary process has requested for PCI mappings. > > > > This patch makes EAL try and map PCI BARs right after the hugepages > > (instead of location chosen by mmap) in virtual memory, so that PCI BARs > > have less chance of ending up in random places in virtual memory. > > > > Signed-off-by: Liang Xu > > Signed-off-by: Anatoly Burakov > > Acked-by: Bruce Richardson Applied Thanks -- Thomas