* [PATCH 1/1] doc: fix acronym for read-modify-write
@ 2014-07-10 19:37 Pranith Kumar
0 siblings, 0 replies; only message in thread
From: Pranith Kumar @ 2014-07-10 19:37 UTC (permalink / raw)
To: trivial, Randy Dunlap, open list:DOCUMENTATION, open list
fix acronym for read-modify-write from RMV to RMW
Signed-off-by: Pranith Kumar <bobby.prani@gmail.com>
---
Documentation/this_cpu_ops.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/this_cpu_ops.txt b/Documentation/this_cpu_ops.txt
index 1a4ce7e..9e44fdf 100644
--- a/Documentation/this_cpu_ops.txt
+++ b/Documentation/this_cpu_ops.txt
@@ -21,7 +21,7 @@ Read-modify-write operations are of particular interest. Frequently
processors have special lower latency instructions that can operate
without the typical synchronization overhead but still provide some
sort of relaxed atomicity guarantee. The x86 for example can execute
-RMV (Read Modify Write) instructions like inc/dec/cmpxchg without the
+RMW (Read Modify Write) instructions like inc/dec/cmpxchg without the
lock prefix and the associated latency penalty.
Access to the variable without the lock prefix is not synchronized but
--
1.9.1
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2014-07-10 19:37 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-07-10 19:37 [PATCH 1/1] doc: fix acronym for read-modify-write Pranith Kumar
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome