DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org, honnappa.nagarahalli@arm.com, ruifeng.wang@arm.com,
	Phil Yang <phil.yang@arm.com>,
	bruce.richardson@intel.com, konstantin.ananyev@intel.com,
	dev@dpdk.org, david.marchand@redhat.com,
	David Christensen <drc@linux.vnet.ibm.com>
Subject: Re: [dpdk-dev] atomic operations
Date: Sun, 04 Jul 2021 02:40:45 +0200	[thread overview]
Message-ID: <1736883.HvhGVPZ4tG@thomas> (raw)
In-Reply-To: <20210703103041.31ee7456@hermes.local>

03/07/2021 19:30, Stephen Hemminger:
> Thomas Monjalon <thomas@monjalon.net> wrote:
> > It is very difficult to find which wrapper to use.
> > 
> > This is the guide we have:
> > https://doc.dpdk.org/guides/prog_guide/writing_efficient_code.html#locks-and-atomic-operations
> > There are 2 blog posts:
> > https://www.dpdk.org/blog/2021/03/26/dpdk-adopts-the-c11-memory-model/
> > https://www.dpdk.org/blog/2021/06/09/reader-writer-concurrency/
> > 
> > Basically it says we should use "__atomic builtins" but there is example
> > for simple situations like counters, memory barriers, etc.
> > Please who could work on improving the documentation?
> 
> Maybe there needs to be a DPDK version of the infamous kernel documentation
> of memory barriers.

No need to provide the whole theory. We can link to good resources
like the kernel documentation you mention, and insist on which function
we should use in DPDK, and explain why/when.



  reply	other threads:[~2021-07-04  0:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-03 11:29 Thomas Monjalon
2021-07-03 17:30 ` Stephen Hemminger
2021-07-04  0:40   ` Thomas Monjalon [this message]
2021-07-04  0:37 ` Thomas Monjalon
2021-07-05  7:00   ` Ruifeng Wang
2021-07-05  7:30     ` Thomas Monjalon
2021-07-05  8:33       ` Ruifeng Wang
2021-07-05 16:20         ` Stephen Hemminger
2021-07-07 19:04 ` Honnappa Nagarahalli
2021-07-07 19:28   ` Thomas Monjalon

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=1736883.HvhGVPZ4tG@thomas \
    --to=thomas@monjalon.net \
    --cc=bruce.richardson@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=drc@linux.vnet.ibm.com \
    --cc=honnappa.nagarahalli@arm.com \
    --cc=konstantin.ananyev@intel.com \
    --cc=phil.yang@arm.com \
    --cc=ruifeng.wang@arm.com \
    --cc=stephen@networkplumber.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).