[dpdk-dev] Fwd: EAL: map_all_hugepages(): mmap failed: Cannot allocate memory

node, DPDK library may be can skipp grabbing memory from these excluded nodes? Just some thoughts. John On Thu, Mar 17, 2016 at 7:51 PM, Tan, Jianfeng wrote: > > > On 3/18/2016 6:41 AM, John Wei wrote: > > I am setting up OVS inside a Linux container. This OVS is built using

[dpdk-dev] Fwd: EAL: map_all_hugepages(): mmap failed: Cannot allocate memory

I am setting up OVS inside a Linux container. This OVS is built using DPDK library. During the startup of ovs-vswitchd, it core dumped due to fail to mmap. in eal_memory.c virtaddr = mmap(vma_addr, hugepage_sz, PROT_READ | PROT_WRITE, MAP_SHARED, fd, 0); This call is

[dpdk-dev] DPDK library grab all the memory during start up

I am setting up open-vswitch with DPDK in container, and running many this OVS/DPDK containers on the same host. OVS in each container will be using differ PCI deviced bound to DPDK. I am using --file-prefix to allow sharing of same /dev/hugepages tlbfs, and using --socket-mem to limit the memory