DPDK patches and discussions
 help / color / mirror / Atom feed
From: Kevin Wilson <wkevils@gmail.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] Error when starting testpmd in dpdk 2.2.0 ("Creation of mbuf pool for socket 0 failed")
Date: Tue, 22 Mar 2016 22:21:28 +0200	[thread overview]
Message-ID: <CAGXs5wXEMPVrurh=R_Y6t4a0mUAohXZFa=uVk3kMueJJeCtKkA@mail.gmail.com> (raw)

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

                 reply	other threads:[~2016-03-22 20:21 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAGXs5wXEMPVrurh=R_Y6t4a0mUAohXZFa=uVk3kMueJJeCtKkA@mail.gmail.com' \
    --to=wkevils@gmail.com \
    --cc=dev@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).