From: Peter Chen <peter.feifan.chen@gmail.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Is rte_mempool library is multi-thread safe ???
Date: Thu, 19 Dec 2013 13:30:42 -0800 [thread overview]
Message-ID: <CAMGYKAfuRdhuydXixJ-ycTQcksRqSKOmFpz8fJGuNZEob04E6Q@mail.gmail.com> (raw)
In-Reply-To: <201312191804.31322.thomas.monjalon@6wind.com>
does that mean that on the same core, we can't do rte_eth_rx_burst in one
thread (I assume this function allocates from mempool for storing mbufs
everytime it receives a packet), while another thread calls
rte_pktmbuf_alloc from the same mem_pool?
On Thu, Dec 19, 2013 at 9:04 AM, Thomas Monjalon
<thomas.monjalon@6wind.com>wrote:
> Hello,
>
> 19/12/2013 11:57, ankit kumar :
> > It was working fine but i am not sure that memory allocation &
> > deallocation in rte_mempool library, is multi-thread safe or not.
>
> From http://dpdk.org/doc/api/rte__mempool_8h.html:
> "the mempool implementation is not preemptable"
> There is more explanations in this email:
> http://dpdk.org/ml/archives/dev/2013-August/000402.html
>
> --
> Thomas
>
next prev parent reply other threads:[~2013-12-19 21:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-19 10:57 ankit kumar
2013-12-19 17:04 ` Thomas Monjalon
2013-12-19 21:30 ` Peter Chen [this message]
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=CAMGYKAfuRdhuydXixJ-ycTQcksRqSKOmFpz8fJGuNZEob04E6Q@mail.gmail.com \
--to=peter.feifan.chen@gmail.com \
--cc=dev@dpdk.org \
--cc=thomas.monjalon@6wind.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).