From: Stephen Hemminger <stephen@networkplumber.org>
To: "Medvedkin, Vladimir" <vladimir.medvedkin@intel.com>
Cc: rajesh goel <rgoel.bangalore@gmail.com>,
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 10:23:16 -0700 [thread overview]
Message-ID: <20240828102316.0a72bbb2@hermes.local> (raw)
In-Reply-To: <SJ0PR11MB5772ECD1C1F31EB64BC048AD96952@SJ0PR11MB5772.namprd11.prod.outlook.com>
On Wed, 28 Aug 2024 15:54:27 +0000
"Medvedkin, Vladimir" <vladimir.medvedkin@intel.com> wrote:
> 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
RCU is always faster than reader/writer locks.
Reader/Writer locks are slower than simple spin lock unless reader holds for a long time.
next prev parent reply other threads:[~2024-08-28 17:23 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
2024-08-28 15:54 ` Medvedkin, Vladimir
2024-08-28 17:23 ` Stephen Hemminger [this message]
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=20240828102316.0a72bbb2@hermes.local \
--to=stephen@networkplumber.org \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=rgoel.bangalore@gmail.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).