From: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
To: Brijesh Singh <brijesh.s.singh@gmail.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: nd <nd@arm.com>
Subject: Re: [dpdk-dev] rte_hash thread safe
Date: Tue, 24 Apr 2018 06:12:44 +0000 [thread overview]
Message-ID: <HE1PR0801MB1930FFADF298642955D8216698880@HE1PR0801MB1930.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <CAAQ1jEFF_MWsM2tSLG+9weh3JQNQkkEk2USJbi3QQxj6wG7C5g@mail.gmail.com>
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.
If T1 is a worker/data plane thread, which is supposed to be pinned to the CPU, is it required to consider the case of T1 getting pre-empted?
However, this case can exist with T1 not getting pre-empted. i.e. Key1 can get deleted by thread T2 while T1 is doing the comparison.
In this case, 'k' is a memory pointer pointing to an array element. The memory itself is not freed. The code will still return the data associated with Key1 - assuming Key2 belongs to a different slot ID. But, it is possible that 'data' may not be valid anymore since it is owned by the application.
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
next prev parent reply other threads:[~2018-04-24 6:12 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
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 [this message]
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=HE1PR0801MB1930FFADF298642955D8216698880@HE1PR0801MB1930.eurprd08.prod.outlook.com \
--to=honnappa.nagarahalli@arm.com \
--cc=brijesh.s.singh@gmail.com \
--cc=dev@dpdk.org \
--cc=nd@arm.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).