From: Andrew Rybchenko <arybchenko@solarflare.com>
To: Ravi Kerur <rkerur@gmail.com>, <dev@dpdk.org>
Subject: Re: [dpdk-dev] Debug crash in bucket_enqueue ()
Date: Thu, 24 Oct 2019 19:58:20 +0300 [thread overview]
Message-ID: <78751ab2-0e3b-4341-4090-bca86b5e1b01@solarflare.com> (raw)
In-Reply-To: <CAFb4SLC6Scm5sRyVqizmcrQoV14XFOzNnAyE21s7mgZRGcpwow@mail.gmail.com>
Hello,
please, see note on the following page:
https://doc.dpdk.org/guides/prog_guide/mempool_lib.html#mempool-handlers
Andrew.
On 10/24/19 7:42 PM, Ravi Kerur wrote:
> DPDK team,
>
> I have a simple multi process setup with OVS/DPDK as primary and another
> process as secondary. OVS/DPDK sets up mempool and rings with MP/MC flags
> and secondary process attaches to it. I have used
> example/multi-process/simple_mp as an example. I have disabled 'ASLR' and
> made sure primary and secondary use distinct EAL lcores.
>
> test case is that for every 10/12 packets OVS/DPDK does
> rte_mempool_get() and rte_ring_enqueue()
> with information about the packets
>
> secondary process does
> rte_ring_dequeue() and rte_mempool_put()
>
> Couple of minutes into the test secondary process crashes with following
> baktrace.
>
> Any other system level settings need to be set or inputs on debugging
> bucket_enqueue?
>
> #0 0x0000555555734160 in bucket_enqueue ()
> #1 0x00005555555edf06 in rte_mempool_ops_enqueue_bulk (mp=0x17fa9ac80,
> obj_table=0x17fac8210, n=16) at
> /home/rkerur/dpdk-stable-18.11.2//x86_64-native-linuxapp-gcc/include/rte_mempool.h:704
> #2 0x00005555555f072a in __mempool_generic_put (cache=0x17fac8100, n=1,
> obj_table=0x7ffff4e09050, mp=0x17fa9ac80) at
> /home/rkerur/dpdk-stable-18.11.2//x86_64-native-linuxapp-gcc/include/rte_mempool.h:1249
> #3 rte_mempool_generic_put (cache=0x17fac8100, n=1,
> obj_table=0x7ffff4e09050, mp=0x17fa9ac80) at
> /home/rkerur/dpdk-stable-18.11.2//x86_64-native-linuxapp-gcc/include/rte_mempool.h:1285
> #4 rte_mempool_put_bulk (n=1, obj_table=0x7ffff4e09050, mp=0x17fa9ac80) at
> /home/rkerur/dpdk-stable-18.11.2//x86_64-native-linuxapp-gcc/include/rte_mempool.h:1308
> #5 rte_mempool_put (obj=0x17f994300, mp=0x17fa9ac80) at
> /home/rkerur/dpdk-stable-18.11.2//x86_64-native-linuxapp-gcc/include/rte_mempool.h:1326
> #6 lcore_recv (arg=0x7fffffffd5b3) at /home/rkerur/simple_mp_ovs/main.c:369
> #7 0x00005555556df8f1 in eal_thread_loop ()
> #8 0x00007ffff72086db in start_thread (arg=0x7ffff4e0b700) at
> pthread_create.c:463
> #9 0x00007ffff6f3188f in clone () at
> ../sysdeps/unix/sysv/linux/x86_64/clone.S:95
>
> Thanks,
> Ravi
next prev parent reply other threads:[~2019-10-24 16:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-24 16:42 Ravi Kerur
2019-10-24 16:58 ` Andrew Rybchenko [this message]
2019-10-24 18:56 ` Ravi Kerur
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=78751ab2-0e3b-4341-4090-bca86b5e1b01@solarflare.com \
--to=arybchenko@solarflare.com \
--cc=dev@dpdk.org \
--cc=rkerur@gmail.com \
/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).