summaryrefslogtreecommitdiff
path: root/fs/binfmt_elf_fdpic.c
diff options
context:
space:
mode:
authorAlan Stern <stern@rowland.harvard.edu>2019-05-03 20:13:44 +0300
committerPaul E. McKenney <paulmck@linux.ibm.com>2019-06-19 19:31:53 +0300
commit2966f8d440c3d2b6ef6c44093a9f9c42701a077a (patch)
tree00e538245c0fb16d6bab0d69d7f2d0c418f6d47c /fs/binfmt_elf_fdpic.c
parent0031e38adf38779acce5737f4905b9f60750b674 (diff)
downloadlinux-2966f8d440c3d2b6ef6c44093a9f9c42701a077a.tar.xz
Documentation: atomic_t.txt: Explain ordering provided by smp_mb__{before,after}_atomic()
The description of smp_mb__before_atomic() and smp_mb__after_atomic() in Documentation/atomic_t.txt is slightly terse and misleading. It does not clearly state which other instructions are ordered by these barriers. This improves the text to make the actual ordering implications clear, and also to explain how these barriers differ from a RELEASE or ACQUIRE ordering. Signed-off-by: Alan Stern <stern@rowland.harvard.edu> Cc: Jonathan Corbet <corbet@lwn.net> Cc: Peter Zijlstra <peterz@infradead.org> Acked-by: Andrea Parri <andrea.parri@amarulasolutions.com> Signed-off-by: Paul E. McKenney <paulmck@linux.ibm.com>
Diffstat (limited to 'fs/binfmt_elf_fdpic.c')
0 files changed, 0 insertions, 0 deletions