From: ankit kumar <akprajapati616@gmail.com>
To: dev <dev@dpdk.org>
Subject: [dpdk-dev] Is rte_mempool library is multi-thread safe ???
Date: Thu, 19 Dec 2013 16:27:59 +0530 [thread overview]
Message-ID: <CAG9qd2pi-Q7LawBymDSsAY3054FUqf7RK0L61oDrsKVY_Q4S0Q@mail.gmail.com> (raw)
Hi,
I was testing rte_ring in DPDK as it provides multi-consumer &
multi-produce queue(lock-free but not wait-free).
It was working fine but i am not sure that memory allocation &
deallocation in rte_mempool library, is multi-thread safe or not.
Because its giving me error during allocation(from
multi-thread) as "Allocation failed(returned pointer is NULL in
allocation function rte_pktmbuf_alloc())" & during rte_pktmbuf_free()
it generates segmentation fault and when i traced out, core file
generated, it indicated that the problem is in rte_pktmbuf_free().
Any help !!!
next reply other threads:[~2013-12-19 10:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-19 10:57 ankit kumar [this message]
2013-12-19 17:04 ` Thomas Monjalon
2013-12-19 21:30 ` Peter Chen
2013-12-20 21:28 ` Olivier MATZ
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=CAG9qd2pi-Q7LawBymDSsAY3054FUqf7RK0L61oDrsKVY_Q4S0Q@mail.gmail.com \
--to=akprajapati616@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).