diff options
author | kib <kib@FreeBSD.org> | 2015-07-30 15:47:53 +0000 |
---|---|---|
committer | kib <kib@FreeBSD.org> | 2015-07-30 15:47:53 +0000 |
commit | 88c35d6516fe8bf221803cefd19bc569dd41d56a (patch) | |
tree | c3f3c6150c26daac2925ea8cd6be6237d465f049 /sys/i386 | |
parent | f4c52859b87baba7030ff64113142879d192f5f6 (diff) | |
download | FreeBSD-src-88c35d6516fe8bf221803cefd19bc569dd41d56a.zip FreeBSD-src-88c35d6516fe8bf221803cefd19bc569dd41d56a.tar.gz |
Improve comments.
Submitted by: bde
MFC after: 2 weeks
Diffstat (limited to 'sys/i386')
-rw-r--r-- | sys/i386/include/atomic.h | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/sys/i386/include/atomic.h b/sys/i386/include/atomic.h index 15742a5..3242d76 100644 --- a/sys/i386/include/atomic.h +++ b/sys/i386/include/atomic.h @@ -259,9 +259,9 @@ atomic_testandset_int(volatile u_int *p, u_int v) * consistent fences in SMP kernels. We use "lock addl $0,mem" for a * Store/Load barrier, as recommended by the AMD Software Optimization * Guide, and not mfence. In the kernel, we use a private per-cpu - * cache line as the target for the locked addition, to avoid - * introducing false data dependencies. In userspace, a word at the - * top of the stack is utilized. + * cache line for "mem", to avoid introducing false data + * dependencies. In user space, we use the word at the top of the + * stack. * * For UP kernels, however, the memory of the single processor is * always consistent, so we only need to stop the compiler from |