From: rajesh goel <rgoel.bangalore@gmail.com>
To: stephen@networkplumber.org
Cc: "Medvedkin, Vladimir" <vladimir.medvedkin@intel.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: Thu, 29 Aug 2024 11:18:35 +0530 [thread overview]
Message-ID: <CANxYqLTXMho4kO1yoML1w4-5pBav+-wX7XDni18=3vCns3u1zQ@mail.gmail.com> (raw)
In-Reply-To: <20240828102316.0a72bbb2@hermes.local>
[-- Attachment #1: Type: text/plain, Size: 1030 bytes --]
Thanks Stephen , Vladimir,
Let me explore DPDK RCU more, if it helps my application.
Will get back with my results.
Regards.
Rajesh
On Wed, Aug 28, 2024 at 10:53 PM Stephen Hemminger <
stephen@networkplumber.org> wrote:
> 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.
>
[-- Attachment #2: Type: text/html, Size: 1504 bytes --]
prev parent reply other threads:[~2024-08-29 7:20 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
2024-08-29 5:48 ` rajesh goel [this message]
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='CANxYqLTXMho4kO1yoML1w4-5pBav+-wX7XDni18=3vCns3u1zQ@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=stephen@networkplumber.org \
--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).