Recent efforts led to the specification of a memory consistency model for the Linux kernel , which "can (roughly speaking) be thought of as an automated version of memory-barriers.txt" and which is (in turn) "accompanied by extensive documentation on its use and its design".
Make sure that the (occasional) reader of memory-barriers.txt will be aware of these developments.  https://marc.info/?l=linux-kernel&m=151687290114799&w=2 Signed-off-by: Andrea Parri <parri.and...@gmail.com> --- Documentation/memory-barriers.txt | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/Documentation/memory-barriers.txt b/Documentation/memory-barriers.txt index a863009849a3b..8cc3f098f4a7d 100644 --- a/Documentation/memory-barriers.txt +++ b/Documentation/memory-barriers.txt @@ -17,7 +17,9 @@ meant as a guide to using the various memory barriers provided by Linux, but in case of any doubt (and there are many) please ask. To repeat, this document is not a specification of what Linux expects from -hardware. +hardware. For such a specification, in the form of a memory consistency +model, and for documentation about its usage and its design, the reader is +referred to "tools/memory-model/". The purpose of this document is twofold: -- 2.7.4 -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html