From: "Van Haaren, Harry" <harry.van.haaren@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: Tom Barbette <barbette@kth.se>,
Perugu Hemasai Chandra Prasad <hemasaiperugu@5g.iith.ac.in>,
"users@dpdk.org" <users@dpdk.org>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-users] [dpdk-dev] Sharing Data structure between logical cores in DPDK- regarding
Date: Fri, 6 Dec 2019 16:51:40 +0000 [thread overview]
Message-ID: <MN2PR11MB4447D38DE69C70948DB0B2D0D75F0@MN2PR11MB4447.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20191206083030.4216fd3e@hermes.lan>
> -----Original Message-----
> From: Stephen Hemminger <stephen@networkplumber.org>
> Sent: Friday, December 6, 2019 4:31 PM
> To: Van Haaren, Harry <harry.van.haaren@intel.com>
> Cc: Tom Barbette <barbette@kth.se>; Perugu Hemasai Chandra Prasad
> <hemasaiperugu@5g.iith.ac.in>; users@dpdk.org; dev@dpdk.org
> Subject: Re: [dpdk-users] [dpdk-dev] Sharing Data structure between logical
> cores in DPDK- regarding
Hey Stephen,
[OT] Please watch your snipping of > characters and Wrote: strings, I'm not the original author of the question, but from snipping it looks like that below.
> On Thu, 5 Dec 2019 10:54:59 +0000
> "Van Haaren, Harry" <harry.van.haaren@intel.com> wrote:
>
> > I have a small doubt, can we share a data structure between
> > > multiple logical cores in DPDK without locking?
>
> Sure, learn to use RCU!!
Good suggestion, apart from Atomics or Mutex based locking schemes, RCU (Read Copy Update) is another method of (semi) synchronizing/sharing data-structures across threads.
DPDK has some RCU mechanics in lib/librte_rcu/ library, perhaps they are of interest. The implementation here is particularly for reclaiming memory after a Quiescent State point has been reached by all threads.
next prev parent reply other threads:[~2019-12-06 16:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-05 10:16 [dpdk-users] " Perugu Hemasai Chandra Prasad
2019-12-05 10:42 ` [dpdk-users] [dpdk-dev] " Tom Barbette
2019-12-05 10:54 ` Van Haaren, Harry
2019-12-06 16:30 ` Stephen Hemminger
2019-12-06 16:51 ` Van Haaren, Harry [this message]
2019-12-06 17:01 ` Stephen Hemminger
2019-12-10 5:56 ` Honnappa Nagarahalli
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=MN2PR11MB4447D38DE69C70948DB0B2D0D75F0@MN2PR11MB4447.namprd11.prod.outlook.com \
--to=harry.van.haaren@intel.com \
--cc=barbette@kth.se \
--cc=dev@dpdk.org \
--cc=hemasaiperugu@5g.iith.ac.in \
--cc=stephen@networkplumber.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).