From: Neil Horman <nhorman@tuxdriver.com>
To: "Saha, Avik (AWS)" <aviksaha@amazon.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Safe practices for adding to rte_table_hash_lru
Date: Wed, 24 Sep 2014 16:11:05 -0400 [thread overview]
Message-ID: <20140924201105.GC4651@hmsreliant.think-freely.org> (raw)
In-Reply-To: <A4A7819F3AE089479B8A88B97202C75D37BE7F88@ex10-mbx-9001.ant.amazon.com>
On Wed, Sep 24, 2014 at 07:38:49PM +0000, Saha, Avik (AWS) wrote:
> Hey guys
> Is it safe to add an entry to the rte_table_hash while the pipeline is being run - for instance if I were to try and add an entry on a port reader action when the packet enters the pipeline?
>
> Thanks
> Avik
>
No, none of the table implementations are currently thread safe. They all
assume that you will do your own locking between threads and processes. There
were a few patches to support thread safety recently, but they are being
reworked currently.
Neil
next prev parent reply other threads:[~2014-09-24 20:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-24 19:38 Saha, Avik (AWS)
2014-09-24 20:11 ` Neil Horman [this message]
2014-09-25 8:03 ` Gray, Mark D
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=20140924201105.GC4651@hmsreliant.think-freely.org \
--to=nhorman@tuxdriver.com \
--cc=aviksaha@amazon.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).