DPDK patches and discussions
 help / color / mirror / Atom feed
From: rajesh goel <rgoel.bangalore@gmail.com>
To: "Medvedkin, Vladimir" <vladimir.medvedkin@intel.com>
Cc: Ferruh Yigit <ferruh.yigit@amd.com>,
	"Wang, Yipeng1" <yipeng1.wang@intel.com>,
	 "Gobriel, Sameh" <sameh.gobriel@intel.com>,
	"Richardson, Bruce" <bruce.richardson@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: Bihash Support in DPDK
Date: Wed, 28 Aug 2024 15:52:09 +0530	[thread overview]
Message-ID: <CANxYqLQg31B1SfNwxW8uyi453K8dtn==evfovSO84D8t0CshdA@mail.gmail.com> (raw)
In-Reply-To: <SJ0PR11MB57723AF388834C3DFAFD349596952@SJ0PR11MB5772.namprd11.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 2681 bytes --]

Thanks Vladimir for the confirmation.
Is there any plan to support bucket level lock support in dpdk hash.

Thanks
Rajesh

On Wed, Aug 28, 2024 at 2:33 PM Medvedkin, Vladimir <
vladimir.medvedkin@intel.com> wrote:

> Hi Rajesh,
>
>
>
> rte_hash does not support per bucket locks, instead it uses global rwlock.
>
> But you can try lock free mode (see documentation, in particular
> RTE_HASH_EXTRA_FLAGS_RW_CONCURRENCY_LF flag)
>
>
>
>
>
> *From:* rajesh goel <rgoel.bangalore@gmail.com>
> *Sent:* Tuesday, August 27, 2024 4:57 PM
> *To:* Medvedkin, Vladimir <vladimir.medvedkin@intel.com>
> *Cc:* Ferruh Yigit <ferruh.yigit@amd.com>; Wang, Yipeng1 <
> yipeng1.wang@intel.com>; Gobriel, Sameh <sameh.gobriel@intel.com>;
> Richardson, Bruce <bruce.richardson@intel.com>; dev@dpdk.org
> *Subject:* Re: Bihash Support in DPDK
>
>
>
> Thanks for the reply.
>
>
>
> Bihash I mean bounded index what Vpp supports.
>
>
>
> Iam looking for the bucket level lock support. Currently Iam using hash
> table shared by multiple process or multiple core/threads. So I have to
> take the write lock by single core and then read lock by multiple cores to
> read the value wrote in this hash table. Multiple readers are getting
> blocked due to this. I want to avoid this to increase performance.
>
>
>
> Let me know your thoughts on this.
>
>
>
> Regards
>
> Rajesh
>
>
>
> On Tue, 27 Aug, 2024, 14:44 Medvedkin, Vladimir, <
> vladimir.medvedkin@intel.com> wrote:
>
> Hi Rajesh,
>
>
>
> Please clarify what do you mean by “bihash”? Bidirectional? Bounded index?
>
>
>
> As for concurrent lookup/updates, yes, DPDK hash table supports
> multi-process/multi-thread, please see the documentation:
>
> https://doc.dpdk.org/guides/prog_guide/hash_lib.html#multi-process-support
>
>
>
>
>
> *From:* rajesh goel <rgoel.bangalore@gmail.com>
> *Sent:* Tuesday, August 27, 2024 7:04 AM
> *To:* Ferruh Yigit <ferruh.yigit@amd.com>
> *Cc:* Wang, Yipeng1 <yipeng1.wang@intel.com>; Gobriel, Sameh <
> sameh.gobriel@intel.com>; Richardson, Bruce <bruce.richardson@intel.com>;
> Medvedkin, Vladimir <vladimir.medvedkin@intel.com>; dev@dpdk.org
> *Subject:* Re: Bihash Support in DPDK
>
>
>
> Hi All,
>
> Can we get some reply.
>
>
>
> Thanks
>
> Rajesh
>
>
>
> On Thu, Aug 22, 2024 at 9:32 PM Ferruh Yigit <ferruh.yigit@amd.com> wrote:
>
> On 8/22/2024 8:51 AM, rajesh goel wrote:
> > Hi All,
> > Need info if DPDK hash library supports bihash table where for multi-
> > thread and multi-process we can update/del/lookup entries per bucket
> level.
> >
> >
>
> + hash library maintainers.
>
>

[-- Attachment #2: Type: text/html, Size: 7577 bytes --]

  reply	other threads:[~2024-08-28 11:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-22  7:51 rajesh goel
2024-08-22 16:02 ` Ferruh Yigit
2024-08-27  6:04   ` rajesh goel
2024-08-27  9:14     ` Medvedkin, Vladimir
2024-08-27 15:57       ` rajesh goel
2024-08-28  9:03         ` Medvedkin, Vladimir
2024-08-28 10:22           ` rajesh goel [this message]
2024-08-28 15:54             ` Medvedkin, Vladimir
2024-08-28 17:23               ` Stephen Hemminger
2024-08-29  5:48                 ` rajesh goel

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='CANxYqLQg31B1SfNwxW8uyi453K8dtn==evfovSO84D8t0CshdA@mail.gmail.com' \
    --to=rgoel.bangalore@gmail.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@amd.com \
    --cc=sameh.gobriel@intel.com \
    --cc=vladimir.medvedkin@intel.com \
    --cc=yipeng1.wang@intel.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).