summaryrefslogtreecommitdiffstats
path: root/kernel/taskstats.c
diff options
context:
space:
mode:
authorOleg Nesterov <oleg@tv-sign.ru>2008-02-23 22:03:29 +0100
committerLinus Torvalds <torvalds@woody.linux-foundation.org>2008-02-24 02:52:36 +0100
commit02c608c1fefe821a4c6fc34c45a0dea3cebf4764 (patch)
tree8fd360da8bc83dd45ecec5621791baa73ddfac70 /kernel/taskstats.c
parentmemcgroup: return negative error code in mem_cgroup_create() (diff)
downloadlinux-02c608c1fefe821a4c6fc34c45a0dea3cebf4764.tar.xz
linux-02c608c1fefe821a4c6fc34c45a0dea3cebf4764.zip
documentation: atomic_add_unless() doesn't imply mb() on failure
(sorry for being offtpoic, but while experts are here...) A "typical" implementation of atomic_add_unless() can return 0 immediately after the first atomic_read() (before doing cmpxchg). In that case it doesn't provide any barrier semantics. See include/asm-ia64/atomic.h as an example. We should either change the implementation, or fix the docs. Signed-off-by: Oleg Nesterov <oleg@tv-sign.ru> Acked-by: Nick Piggin <npiggin@suse.de> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'kernel/taskstats.c')
0 files changed, 0 insertions, 0 deletions