Re: [PATCH] Document Linux's memory barriers

[Roberto Nibali <ratz@drugphish.ch>]

>>The attached patch documents the Linux kernel's memory barriers.
> 
> References:
> 
> AMD64 Architecture Programmer's Manual Volume 2: System Programming
>         Chapter 7.1: Memory-Access Ordering
>         Chapter 7.4: Buffering and Combining Memory Writes
> 
> IA-32 Intel Architecture Software Developer’s Manual, Volume 3:
> System Programming Guide
>         Chapter 7.1: Locked Atomic Operations
>         Chapter 7.2: Memory Ordering
>         Chapter 7.4: Serializing Instructions

Do you guys reckon it might be worthwhile adding Sparc's sequential 
consistency, TSO, RMO and PSO models, although I think only RMO is used 
in the Linux kernel? References can be found for example in:

   Solaris Internals, Core Kernel Architecture, p63-68:
           Chapter 3.3: Hardware Considerations for Locks and
                        Synchronization

   Unix Systems for Modern Architectures, Symmetric Multiprocessing
   and Caching for Kernel Programmers:
           Chapter 13 : Other Memory Models

Or is DaveM the only one fiddling with Sparc memory barriers implementation?

Regards,
Roberto Nibali, ratz
-- 
echo 
'[q]sa[ln0=aln256%Pln256/snlbx]sb3135071790101768542287578439snlbxq' | dc