[<prev] [next>] [day] [month] [year] [list]
Message-Id: <1405021052-8760-1-git-send-email-bobby.prani@gmail.com>
Date: Thu, 10 Jul 2014 15:37:32 -0400
From: Pranith Kumar <bobby.prani@...il.com>
To: trivial@...nel.org, Randy Dunlap <rdunlap@...radead.org>,
linux-doc@...r.kernel.org (open list:DOCUMENTATION),
linux-kernel@...r.kernel.org (open list)
Subject: [PATCH 1/1] doc: fix acronym for read-modify-write
fix acronym for read-modify-write from RMV to RMW
Signed-off-by: Pranith Kumar <bobby.prani@...il.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists