From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: j.alglave@ucl.ac.uk, luc.maranget@inria.fr,
parri.andrea@gmail.com, stern@rowland.harvard.edu,
dhowells@redhat.com, peterz@infradead.org, will.deacon@arm.com,
boqun.feng@gmail.com, npiggin@gmail.com
Cc: linux-kernel@vger.kernel.org
Subject: Memory-ordering recipes
Date: Sun, 17 Sep 2017 16:05:09 -0700 [thread overview]
Message-ID: <20170917230509.GA21394@linux.vnet.ibm.com> (raw)
Hello!
The topic of memory-ordering recipes came up at the Linux Plumbers
Conference microconference on Friday, so I thought that I should summarize
what is currently "out there":
1. memory-barriers.txt: A bit rambling and diffuse for a recipes
document.
2. https://www.kernel.org/pub/linux/kernel/people/paulmck/LWNLinuxMM/Examples.html
Many of the examples are on-point, but this is aimed more
at understanding the memory model than at an organized set
of recipes.
3. https://www.kernel.org/pub/linux/kernel/people/paulmck/LWNLinuxMM/Examples.html
Slides 15-20. Again, some of the litmus tests are on-point,
but the focus is more on understanding the memory model than on
an organized set of recipes.
So what litmus tests are needed? Here is my initial set:
1. Release-acquire chains, AKA ISA2, Z6.2, LB, and 3.LB
Lots of variety here, can in some cases substitute:
a. READ_ONCE() for smp_load_acquire()
b. WRITE_ONCE() for smp_store_release()
c. Dependencies for both smp_load_acquire() and
smp_store_release().
d. smp_wmb() for smp_store_release() in first thread
of ISA2 and Z6.2.
e. smp_rmb() for smp_load_acquire() in last thread of ISA2.
2. MP (see test6.pdf for nickname translation)
a. smp_store_release() / smp_load_acquire()
b. rcu_assign_pointer() / rcu_dereference()
c. smp_wmb() / smp_rmb()
d. Replacing either of the above with smp_mb()
3. SB
a. smp_mb(), as in lockless wait-wakeup coordination.
And as in sys_membarrier()-scheduler coordination,
for that matter.
Others?
Thanx, Paul
next reply other threads:[~2017-09-17 23:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-17 23:05 Paul E. McKenney [this message]
2017-09-18 7:52 ` Memory-ordering recipes Boqun Feng
2017-09-18 14:25 ` Paul E. McKenney
2017-09-19 2:00 ` Boqun Feng
2017-09-21 12:45 ` Peter Zijlstra
2017-09-21 15:26 ` Paul E. McKenney
2017-09-21 16:15 ` Peter Zijlstra
2017-09-21 16:40 ` Paul E. McKenney
2017-09-22 9:29 ` Peter Zijlstra
2017-09-22 21:06 ` Paul E. McKenney
2017-10-17 21:01 ` Paul E. McKenney
2017-10-18 1:07 ` Andrea Parri
2017-10-18 20:48 ` Paul E. McKenney
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=20170917230509.GA21394@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=boqun.feng@gmail.com \
--cc=dhowells@redhat.com \
--cc=j.alglave@ucl.ac.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=luc.maranget@inria.fr \
--cc=npiggin@gmail.com \
--cc=parri.andrea@gmail.com \
--cc=peterz@infradead.org \
--cc=stern@rowland.harvard.edu \
--cc=will.deacon@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.