From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 34148A0540; Wed, 6 Jul 2022 15:38:09 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id CA73E40691; Wed, 6 Jul 2022 15:38:08 +0200 (CEST) Received: from mail-pf1-f182.google.com (mail-pf1-f182.google.com [209.85.210.182]) by mails.dpdk.org (Postfix) with ESMTP id F016E40150 for ; Wed, 6 Jul 2022 15:38:06 +0200 (CEST) Received: by mail-pf1-f182.google.com with SMTP id 3so4264352pfx.3 for ; Wed, 06 Jul 2022 06:38:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=NDMf4S+zCDxHMTqO6oH6IiPspl8blSV1CVvw7hXeLDg=; b=eDto4ReyYpa+h4aCaydK4HU3jXw82q/wZUNztO3uO30rPVwmcRUaWsknBv3NpXIR4c vncArl8pb1XcdGPWuyhsj08GkvBZHzw1rjzloY+re8EuYJlqvWO5BX5Pvyz21MCVV2pO 7T1dzkW64Mdx0MDI/Cd3UnDj6zQfzEtRngmbU7S+xzjBE8hIwKjAh0PAuY9pKwumw9zE WACVcJIdZwUfZG2PT41lFFMouF/yIUwVE8AFvPJ4feVsfU+JrLSPPYk0mYRtiGRduNol jaUYBLlslk4qJuAbuaburBp4nkNJgmjuVL/zhFLYNrKlZOZLkWWOkYU5ajMWDwH+OdO7 9knQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=NDMf4S+zCDxHMTqO6oH6IiPspl8blSV1CVvw7hXeLDg=; b=5kqxoQlOsx+CsQQIaKBzyubeyPHN30syMmLrCyRYLRWOCkP+ekvj1MMmc1oPKtwWzt 99+TyUU8mfGnyyqsJJxVpw5ZWaRhAv6pCtWR63dUlVqILCMd93aWryy8uEh9f25YG2Hs +0Npv4wxwCbFq74SvfTk9QWb/nRkjY/PW+6HLrpmUl1HfWZIP5uwY2qRnRp8XiGoEInc es88prhkUouH4xHb6uTEXLYAKbnKg7aPMBKjfbGds5g4BVBfCzCsdgBCIe3O3fFXrE2X D9k4XXQAMgAdS+BoN7WXg+EMO+9Qaq7rTc/weEfrXQXea3p4DCGkqMjbNnHwuqomnXii 4QAQ== X-Gm-Message-State: AJIora8zJqm/0J+ggtSpsjUS56aWNgT3+26ItbqiLjUYbtD4b78ldINl Kq6aZYR6G2xzIu2NGR/uLLeTTIxO24+R1opfSPULdDdq/0M= X-Google-Smtp-Source: AGRyM1uPNNgxLrh43edKeLEOkGYejrnvvZPqnZ0AdEudLKzfXuWhSP1Fmf/9RDVH0cqDoz5oNOP7LXYhmStGhj8fANg= X-Received: by 2002:a63:2014:0:b0:411:90a4:6e9c with SMTP id g20-20020a632014000000b0041190a46e9cmr31260435pgg.500.1657114685673; Wed, 06 Jul 2022 06:38:05 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: venkatesh bs Date: Wed, 6 Jul 2022 19:07:54 +0530 Message-ID: Subject: Re: clarification on RTE_HASH_EXTRA_FLAGS_RW_CONCURRENCY_LF flag To: dev@dpdk.org Content-Type: multipart/alternative; boundary="00000000000031166205e32314dd" X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org --00000000000031166205e32314dd Content-Type: text/plain; charset="UTF-8" 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 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. > --00000000000031166205e32314dd Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi All,

In multithreaded/= Multicore=C2=A0 environment=C2=A0can we use=C2=A0RTE_HASH_EXTRA_F= LAGS_RW_CONCURRENCY_LF independently,=C2=A0
or this flag should always be used with=C2=A0RTE_HASH_EXTRA_FLAGS_MULTI_WRITER_ADD.

We are trying to create and access the hash tabl= e with=C2=A0RTE_HASH_EXTRA_FLAGS_RW_CONCURRENCY_LF only.
We are getting cr= ashes in multi core environments , we debugged nothing wrong in the applica= tion , everything looks good.

We call=C2=A0rte_hash_del_key() first and from the returned posi= tion we are calling=C2=A0rte_hash_free_key_with_position().

P= lease let me know if we missed something.

Thanks,
Venkatesh.

On Wed, Jul 6, 2022 = at 9:15 AM venkatesh bs <venki.bs= v@gmail.com> wrote:
Hi All,

In mul= tithreaded/Multicore=C2=A0 environment=C2=A0can we use=C2=A0RTE_H= ASH_EXTRA_FLAGS_RW_CONCURRENCY_LF independently,=C2=A0
<= div>or this flag should always be used w= ith=C2=A0RTE_HASH_EXTRA_FLAGS_MULTI_WRITER_ADD.

We are trying to create and access th= e hash table with=C2=A0RTE_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=C2=A0rte_hash_del_key() first and from the ret= urned position we are calling=C2=A0rte_hash_free_key_with_position().

Please let me know if we missed something.

Thanks,
Venkatesh.
--00000000000031166205e32314dd--