From: Stephen Hemminger <stephen@networkplumber.org>
To: Jim Murphy <jmurphy@arista.com>
Cc: Brijesh Singh <brijesh.s.singh@gmail.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] rte_hash thread safe
Date: Mon, 23 Apr 2018 17:30:34 -0700 [thread overview]
Message-ID: <20180423173034.7086b772@xeon-e3> (raw)
In-Reply-To: <CAJC5fi33YBnE0H-Ug0DONx_QFtTcNO-ga+3k9t9_9b=i+1xr0A@mail.gmail.com>
On Mon, 23 Apr 2018 17:21:15 -0700
Jim Murphy <jmurphy@arista.com> wrote:
> Has anyone seen performance data comparing rte_hash (perhaps with r/w
> locks) versus URCU hash?
>
>
> On Mon, Apr 23, 2018 at 4:50 PM, Stephen Hemminger <
> stephen@networkplumber.org> wrote:
>
> > On Mon, 23 Apr 2018 12:40:41 -0700
> > Brijesh Singh <brijesh.s.singh@gmail.com> wrote:
> >
> > > A gentle reminder,
> > >
> > > I am curious to know if/how rte_hash is thread safe for lookups.It is
> > > not obvious to me how following code is thread safe:
> > >
> > > _rte_hash_lookup_with_hash(const struct rte_hash *h, const void *key,
> > >
> > > hash_sig_t sig, void **data)
> > >
> > > {
> > >
> > >
> > >
> > > …
> > >
> > > if (rte_hash_cmp_eq(key, k->key, h) == 0) {
> > >
> > > if (data != NULL)
> > >
> > > *data = k->pdata;
> > >
> > > }
> > >
> > > a key could be deleted and another key inserted in its slot while the
> > > lookup is happening. For example, in the following sequence of events:
> > > The slot has Key1,V1
> > > Lookup Thread T1 compares the input key to Key1 and it matches. The
> > > thread gets context switched out
> > > Thread T2 deletes Key1.
> > > Thread T2 inserts Key2 with value V2.
> > > T1 reads the data from the slot and returns V2. This is incorrect.
> > >
> > >
> > > Regards,
> > > Brijesh
> > >
> > > On Wed, Apr 11, 2018 at 9:12 PM, Brijesh Singh
> > > <brijesh.s.singh@gmail.com> wrote:
> > > > Hello,
> > > >
> > > > I want to use DPDK's rte_hash library to keep track of tcp flows. The
> > > > lookups will be done by multiple threads but inserts will be done only
> > > > on one thread.
> > > >
> > > > As per the documentation rte_hash library has thread safe lookups. Key
> > > > /data inserts should be done on single thread, since those operations
> > > > are not thread safe. Is this documentation still correct?
> > > >
> > > > The lookup code compares the key and returns the data if the key
> > > > matches, this doesn't look like thread safe. Am I missing something?
> > > >
> > > > _rte_hash_lookup_with_hash(const struct rte_hash *h, const void *key,
> > > >
> > > > hash_sig_t sig, void **data)
> > > >
> > > > {
> > > >
> > > >
> > > >
> > > > …
> > > >
> > > > if (rte_hash_cmp_eq(key, k->key, h) == 0) {
> > > >
> > > > if (data != NULL)
> > > >
> > > > *data = k->pdata;
> > > >
> > > > }
> > > >
> > > > Regards,
> > > > Brijesh
> >
> > The best way to handle this is to do some kind of Read Copy Update.
> > Unfortunately, this is not possible in scope of DPDK since it requires
> > cooperation from application threads.
> >
> > If you need thread safe hash table, my recommendation would be to
> > skip the DPDK hash library and use userspace RCU instead:
> > http://liburcu.org/
> >
> > Note: URCU is LGPL versus BSD licensed. But then any non trivial
> > Linux application needs to use LGPL libraries already.
> >
No. But R/W locks are really slow. Look at one of Paul Mc Kenney's many RCU
talks and papers.
next prev parent reply other threads:[~2018-04-24 0:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-12 4:12 Brijesh Singh
2018-04-23 19:40 ` Brijesh Singh
2018-04-23 23:50 ` Stephen Hemminger
2018-04-24 0:21 ` Jim Murphy
2018-04-24 0:30 ` Stephen Hemminger [this message]
2018-04-24 0:48 ` Jim Murphy
2018-04-24 1:14 ` Stephen Hemminger
2018-04-24 2:13 ` Jim Murphy
2018-04-24 6:36 ` Honnappa Nagarahalli
2018-04-24 15:04 ` Brijesh Singh
2018-04-25 6:45 ` Shyam Shrivastav
2018-04-24 3:48 ` Jerin Jacob
2018-04-24 5:02 ` Stephen Hemminger
2018-04-24 6:12 ` Honnappa Nagarahalli
2018-04-24 11:03 ` Ananyev, Konstantin
2018-04-24 11:07 ` Bruce Richardson
2018-05-24 17:35 ` Wang, Yipeng1
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=20180423173034.7086b772@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=brijesh.s.singh@gmail.com \
--cc=dev@dpdk.org \
--cc=jmurphy@arista.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).