Re: [PATCH] Documentation: memory barrier semantics of atomic_xchg

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Dec 13, 2012 at 11:07:32AM +0100, Richard Braun wrote:
> 
> Signed-off-by: Richard Braun <rbraun@xxxxxxxxx>

Queued for 3.9, thank you!

							Thanx, Paul

> ---
>  Documentation/atomic_ops.txt      |    2 ++
>  Documentation/memory-barriers.txt |    1 +
>  2 files changed, 3 insertions(+), 0 deletions(-)
> 
> diff --git a/Documentation/atomic_ops.txt b/Documentation/atomic_ops.txt
> index 27f2b21..d9ca5be 100644
> --- a/Documentation/atomic_ops.txt
> +++ b/Documentation/atomic_ops.txt
> @@ -253,6 +253,8 @@ This performs an atomic exchange operation on the atomic variable v, setting
>  the given new value.  It returns the old value that the atomic variable v had
>  just before the operation.
> 
> +atomic_xchg requires explicit memory barriers around the operation.
> +
>  	int atomic_cmpxchg(atomic_t *v, int old, int new);
> 
>  This performs an atomic compare exchange operation on the atomic value v,
> diff --git a/Documentation/memory-barriers.txt b/Documentation/memory-barriers.txt
> index 2759f7c..3ed5454 100644
> --- a/Documentation/memory-barriers.txt
> +++ b/Documentation/memory-barriers.txt
> @@ -1684,6 +1684,7 @@ explicit lock operations, described later).  These include:
> 
>  	xchg();
>  	cmpxchg();
> +	atomic_xchg();
>  	atomic_cmpxchg();
>  	atomic_inc_return();
>  	atomic_dec_return();
> -- 
> 1.7.2.5
> 

--
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


[Index of Archives]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Linux FS]     [Yosemite Forum]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]     [Linux Resources]

  Powered by Linux