Re: [dpdk-dev] [PATCH 2/2] eal: use base address hint to reserve space for mem config

On 29-Jul-19 12:18 PM, Anatoly Burakov wrote: Currently, mem config will be mapped without using the virtual area reservation infrastructure, which means it will be mapped at an arbitrary location. This may cause failures to map the shared config in secondary process due to things like PCI whitel

[dpdk-dev] [PATCH 2/2] eal: use base address hint to reserve space for mem config

Currently, mem config will be mapped without using the virtual area reservation infrastructure, which means it will be mapped at an arbitrary location. This may cause failures to map the shared config in secondary process due to things like PCI whitelist arguments allocating memory in a space where