From: Manish Kumar <manish.jangid08@gmail.com>
To: users@dpdk.org
Subject: [dpdk-users] rte_pktmbuf_alloc stuck forever in dpdk 18.05.1
Date: Fri, 1 Feb 2019 16:25:22 +0530 [thread overview]
Message-ID: <CAB107XBdrD8FKkwa06jEKS_ZjYzZqXozaTdGPKHc80tMoKJuWQ@mail.gmail.com> (raw)
Hello Team,
I have been trying dpdk 18.05.1 on a small project which was first written
for dpdk 16.11 release.
It is a primary secondary process architecture where primary process is
reading from the NIC and then sending it to secondary process where I am
calling rte_pktmbuf_alloc for a mempool which was created in the primary
process. In dpdk 16.11 eveything is working fine, however in dpdk 18.05.1 ,
as soon as rte_pktmbuf_alloc API is called, it gets stuck in stack_dequeue
function and keeps in that state forever. Can anybody help in identifying
what could be causing it.
#0 0x00007f7ef232d9e0 in stack_dequeue ()
from /usr/lib64/librte_mempool_stack.so.1.1
#1 0x00000000004110de in rte_mempool_ops_dequeue_bulk (n=33,
obj_table=0x7f4f0c735450, mp=0x7f4f0c6fef00)
at
/home/manishk/dpdk-latest/x86_64-native-linuxapp-gcc/include/rte_mempool.h:679
#2 __mempool_generic_get (cache=0x7f4f0c735440, n=1,
obj_table=0x7f7ee9d41b18, mp=0x7f4f0c6fef00)
at
/home/manishk/dpdk-latest/x86_64-native-linuxapp-gcc/include/rte_mempool.h:1495
#3 rte_mempool_generic_get (cache=0x7f4f0c735440, n=1,
obj_table=0x7f7ee9d41b18, mp=0x7f4f0c6fef00)
at
/home/manishk/dpdk-latest/x86_64-native-linuxapp-gcc/include/rte_mempool.h:1558
#4 rte_mempool_get_bulk (n=1, obj_table=0x7f7ee9d41b18, mp=0x7f4f0c6fef00)
at
/home/manishk/dpdk-latest/x86_64-native-linuxapp-gcc/include/rte_mempool.h:1591
#5 rte_mempool_get (obj_p=0x7f7ee9d41b18, mp=0x7f4f0c6fef00)
at
/home/manishk/dpdk-latest/x86_64-native-linuxapp-gcc/include/rte_mempool.h:1617
#6 rte_mbuf_raw_alloc (mp=0x7f4f0c6fef00)
at
/home/manishk/dpdk-latest/x86_64-native-linuxapp-gcc/include/rte_mbuf.h:992
#7 rte_pktmbuf_alloc (mp=0x7f4f0c6fef00)
at
/home/manishk/dpdk-latest/x86_64-native-linuxapp-gcc/include/rte_mbuf.h:1253
Thank you so much in advance.
Thanks
Manish
reply other threads:[~2019-02-01 10:55 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=CAB107XBdrD8FKkwa06jEKS_ZjYzZqXozaTdGPKHc80tMoKJuWQ@mail.gmail.com \
--to=manish.jangid08@gmail.com \
--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).