From: Rob Zimmerman <rob@thezims.net>
To: users@dpdk.org
Subject: [dpdk-users] Segfault in rte_ring_create
Date: Thu, 15 Sep 2016 13:15:38 -0400 [thread overview]
Message-ID: <CAG0K5qt0KFhCepQaPTS2sAZ7ghnKXkj-kJHp3kc99wjD4H1f6Q@mail.gmail.com> (raw)
Howdy everyone!
Has anyone experienced a segfault in rte_ring_create which looks like the
following bt? Surely, this must be something with my environment and not my
version of DPDK (16.07).
(gdb) bt
#0 ___vfprintf_chk (fp=0x0, flag=1, format=0x599b50 "RING: Cannot reserve
memory for tailq\n", ap=0x7fff25c07990) at vfprintf_chk.c:29
#1 0x000000000046c9fc in rte_vlog ()
#2 0x0000000000424944 in rte_log ()
#3 0x00000000004606f0 in rte_ring_create ()
I checked my hugetables and everything looks like it should be OK (via
dpdk-setup.sh)
AnonHugePages: 8192 kB
HugePages_Total: 512
HugePages_Free: 0
HugePages_Rsvd: 0
HugePages_Surp: 0
Hugepagesize: 2048 kB
The call is made like so:
struct rte_ring *pRing = rte_ring_create("TEST RING", 64, SOCKET_ID_ANY, 0);
As a side note, I actually hit this when trying to create a hash
(rte_hash_create) which ends up calling this under the hood.
Many thanks!
next reply other threads:[~2016-09-15 17:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-15 17:15 Rob Zimmerman [this message]
[not found] ` <65CBCC72-7E80-4A2D-BA95-E773304C329D@net.in.tum.de>
2016-09-15 21:18 ` Rob Zimmerman
2016-09-15 21:54 ` Paul Emmerich
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=CAG0K5qt0KFhCepQaPTS2sAZ7ghnKXkj-kJHp3kc99wjD4H1f6Q@mail.gmail.com \
--to=rob@thezims.net \
--cc=users@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).