diff --git a/Lockless-Patterns%3A-Relaxed-Access-And-Partial-Memory-Limitations.md b/Lockless-Patterns%3A-Relaxed-Access-And-Partial-Memory-Limitations.md new file mode 100644 index 0000000..f1f5b15 --- /dev/null +++ b/Lockless-Patterns%3A-Relaxed-Access-And-Partial-Memory-Limitations.md @@ -0,0 +1 @@ +
Memory barriers are an old acquaintance for some Linux kernel programmers. The first doc vaguely resembling a specification of what one might anticipate from concurrent accesses to knowledge in the kernel is, the truth is, referred to as memory-obstacles.txt. That document describes many kinds of memory obstacles, together with the expectations that Linux has concerning the properties of data and management dependencies. It additionally describes "memory-barrier pairing" \ No newline at end of file