DPDK patches and discussions
 help / color / mirror / Atom feed
* [dpdk-dev] Error when starting testpmd in dpdk 2.2.0 ("Creation of mbuf pool for socket 0 failed")
@ 2016-03-22 20:21 Kevin Wilson
  0 siblings, 0 replies; only message in thread
From: Kevin Wilson @ 2016-03-22 20:21 UTC (permalink / raw)
  To: dev

Hi,

I am getting the following error while running testpmd:

RING: Cannot reserve memory

EAL: Error - exiting with code: 1
  Cause: **** Creation of mbuf pool for socket 0 failed

I am running it thus:

build/app/testpmd --log-level 8 -c7 -n3 -- \
  -i --nb-cores=2 --nb-ports=2 --pkt-filter-mode=perfect

And I followed the instruction on http://dpdk.org/doc/quick-start

However, on my machine, as opposed to what appears in the link above,
there is no

/sys/devices/system/node/node0/hugepages/hugepages-2048kB/nr_hugepage

, and under /sys/devices/system/node I have only a single node called "node1".

I don't know what is the reason for this, this is Fedora 23 x86_64
standard distro and a standard kernel (4.2.3-300.fc23.x86_64), and on
a different machine I **do** have node0.

So instead

echo 64 > /sys/devices/system/node/node0/hugepages/hugepages-2048kB/nr_hugepages

I run

echo 64 > /sys/devices/system/node/node1/hugepages/hugepages-2048kB/nr_hugepages

Could this be related somehow to the problem I have ?

More info:
This is a 16 core machine.

I also delved a bit into the code and added a debug message which
prints the pool name in the method where the failure occur,
mbuf_pool_create(),  and this is what I see:

calling rte_pktmbuf_pool_create(), pool_name=mbuf_pool_socket_0 in
mbuf_pool_create

Any ideas ?

Regards,
Kevin

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2016-03-22 20:21 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-03-22 20:21 [dpdk-dev] Error when starting testpmd in dpdk 2.2.0 ("Creation of mbuf pool for socket 0 failed") Kevin Wilson

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).