From: Jyotiswarup Raiturkar <jyotisr5@googlemail.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] rte_mempools / rte_rings thread safe?
Date: Sat, 28 Dec 2013 20:25:00 +0530 [thread overview]
Message-ID: <CAJn5u1kp96XSMh+=WZ8Sc22-sML__7pjg3JgkNF6CiRY+Yk5pw@mail.gmail.com> (raw)
Hi
The rte_mempool and rte_ring libs have multi-producer/multi-consumer
versions. But it's also mentioned in the header files that the
implementation is not pre-emtable : " Note: the mempool implementation is
not preemptable. A lcore must not be interrupted by another task that uses
the same mempool (because it uses a ring which is not preemptable)"
I had some questions on the same :
- Does having mutually exclusive core masks for a set of threads which use
the ring/mempool suffice for thread safety ( threads will have different
core ids but they will not be pinned to cores) ?
- If i want to use this data structures in a pthread ( created outside of
DPDK environment), is it ok to use this if i do
"RTE_DEFINE_PER_LCORE(unsigned, _lcore_id);" with a core_id exclusive of
all other core masks for DPDK processes.
-Jyoti
next reply other threads:[~2013-12-28 14:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-28 14:55 Jyotiswarup Raiturkar [this message]
2014-01-07 14:27 ` 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='CAJn5u1kp96XSMh+=WZ8Sc22-sML__7pjg3JgkNF6CiRY+Yk5pw@mail.gmail.com' \
--to=jyotisr5@googlemail.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).