Memory obstacles are an old acquaintance for some Linux kernel programmers. The first doc vaguely resembling a specification of what one might expect from concurrent accesses to knowledge within the kernel is, the truth is, called memory-obstacles.txt. That document describes many kinds of memory boundaries, together with the expectations that Linux has regarding the properties of data and management dependencies. It also describes "memory-barrier pairing"