[dpdk-dev] problem: Cannot allocate memzone for ethernet port data

2015-04-22 Thread ChenXiaodong
> > Core 0 [0, 4] > > > > Core 1 [1, 5] > > > > Core 2 [2, 6] > > > > Core 3 [3, 7] > > > > [root at test dpdk-2.0.0]# cat > > /sys/devices/system/node/node0/hugepages/hugepages-2048kB/

[dpdk-dev] problem: Cannot allocate memzone for ethernet port data

2015-04-22 Thread ChenXiaodong
ges-2048kB/nr_hugepages 1024 > From: pablo.de.lara.guarch at intel.com > To: ch.xd at live.cn; dev at dpdk.org > Subject: RE: [dpdk-dev] problem: Cannot allocate memzone for ethernet port > data > Date: Wed, 22 Apr 2015 11:01:08 + > > Hi , > > > -Original Messag

[dpdk-dev] problem: Cannot allocate memzone for ethernet port data

2015-04-22 Thread ChenXiaodong
Hi, every one Is there any one who can help me ? I'm new to DPDK, here is a problem that I don't know how to deal with. The program is running on an machine with two Intel 82576 NICs. One of the NICs is binded with the uio_pci_generic driver?1024 2M hugepages have been setup. Any suggestion

[dpdk-dev] problem: Cannot allocate memzone for ethernet port data

2015-04-22 Thread Bruce Richardson
gt; /sys/devices/system/node/node0/hugepages/hugepages-2048kB/nr_hugepages > 1024 > > > From: pablo.de.lara.guarch at intel.com > > To: ch.xd at live.cn; dev at dpdk.org > > Subject: RE: [dpdk-dev] problem: Cannot allocate memzone for ethernet port > > data > > Date: Wed, 22 Apr

[dpdk-dev] problem: Cannot allocate memzone for ethernet port data

2015-04-22 Thread De Lara Guarch, Pablo
Hi , > -Original Message- > From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of ChenXiaodong > Sent: Wednesday, April 22, 2015 11:33 AM > To: dev at dpdk.org > Subject: [dpdk-dev] problem: Cannot allocate memzone for ethernet port > data > > Hi, every one &

[dpdk-dev] problem: Cannot allocate memzone for ethernet port data

2015-04-22 Thread Stephen Hemminger
On Wed, 22 Apr 2015 14:34:17 +0100 Bruce Richardson wrote: > On Wed, Apr 22, 2015 at 07:36:59PM +0800, ChenXiaodong wrote: > > Thanks for you reply! There is actually only one NUMA node. here is what > > the commands return: > > > > Hi, > > there seems to be a mismatch in terms of the numa n