On Thu, 10 Jul 2014, Pranith Kumar wrote: > fix acronym for read-modify-write from RMV to RMW > > Signed-off-by: Pranith Kumar <bobby.prani@xxxxxxxxx> > --- > 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. Applied. -- Jiri Kosina SUSE Labs -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
