From: venkatesh bs <venki.bsv@gmail.com>
To: dev@dpdk.org, users@dpdk.org
Subject: Re: clarification on RTE_HASH_EXTRA_FLAGS_RW_CONCURRENCY_LF flag
Date: Wed, 6 Jul 2022 19:51:24 +0530 [thread overview]
Message-ID: <CAM3UhOjyVa+exY472yTkPz51J6TZvbCqyibH0uA2NPzOBvc=DQ@mail.gmail.com> (raw)
In-Reply-To: <CAM3UhOh04CFR16puEnQ0YVso8ucvanpJBsyW+-KxV0yJewXovg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2029 bytes --]
Hi All,
In multithreaded/Multicore environment can we use
RTE_HASH_EXTRA_FLAGS_RW_CONCURRENCY_LF
independently,
or this flag should always be used with
RTE_HASH_EXTRA_FLAGS_MULTI_WRITER_ADD.
We are trying to create and access the hash table with
RTE_HASH_EXTRA_FLAGS_RW_CONCURRENCY_LF
only.
We are getting crashes in multi core environments , we debugged nothing
wrong in the application , everything looks good.
We call rte_hash_del_key() first and from the returned position we are
calling rte_hash_free_key_with_position().
Please let me know if we missed something.
Thanks,
Venkatesh.
On Wed, Jul 6, 2022 at 7:07 PM venkatesh bs <venki.bsv@gmail.com> wrote:
> Hi All,
>
> In multithreaded/Multicore environment can we use RTE_HASH_EXTRA_FLAGS_RW_CONCURRENCY_LF
> independently,
> or this flag should always be used with
> RTE_HASH_EXTRA_FLAGS_MULTI_WRITER_ADD.
>
> We are trying to create and access the hash table with RTE_HASH_EXTRA_FLAGS_RW_CONCURRENCY_LF
> only.
> We are getting crashes in multi core environments , we debugged nothing
> wrong in the application , everything looks good.
>
> We call rte_hash_del_key() first and from the returned position we are
> calling rte_hash_free_key_with_position().
>
> Please let me know if we missed something.
>
> Thanks,
> Venkatesh.
>
> On Wed, Jul 6, 2022 at 9:15 AM venkatesh bs <venki.bsv@gmail.com> wrote:
>
>> Hi All,
>>
>> In multithreaded/Multicore environment can we use RTE_HASH_EXTRA_FLAGS_RW_CONCURRENCY_LF
>> independently,
>> or this flag should always be used with
>> RTE_HASH_EXTRA_FLAGS_MULTI_WRITER_ADD.
>>
>> We are trying to create and access the hash table with RTE_HASH_EXTRA_FLAGS_RW_CONCURRENCY_LF
>> only.
>> We are getting crashes in multi core environments , we debugged nothing
>> wrong in the application , everything looks good.
>>
>> We call rte_hash_del_key() first and from the returned position we are
>> calling rte_hash_free_key_with_position().
>>
>> Please let me know if we missed something.
>>
>> Thanks,
>> Venkatesh.
>>
>
[-- Attachment #2: Type: text/html, Size: 6698 bytes --]
parent reply other threads:[~2022-07-06 14:21 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CAM3UhOh04CFR16puEnQ0YVso8ucvanpJBsyW+-KxV0yJewXovg@mail.gmail.com>]
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='CAM3UhOjyVa+exY472yTkPz51J6TZvbCqyibH0uA2NPzOBvc=DQ@mail.gmail.com' \
--to=venki.bsv@gmail.com \
--cc=dev@dpdk.org \
--cc=users@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).