memory-barriers: Fix description of data dependency barriers
In the description of data dependency barriers the words 'before' is used erroneously. Since such barrier order dependent loads one after the other. So substitute 'before' with 'after'. Signed-off-by: Nikolay Borisov <nborisov@suse.com> Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com> Acked-by: Peter Zijlstra <peterz@infradead.org> Cc: Linus Torvalds <torvalds@linux-foundation.org> Cc: Thomas Gleixner <tglx@linutronix.de> Cc: akiyks@gmail.com Cc: boqun.feng@gmail.com Cc: dhowells@redhat.com Cc: j.alglave@ucl.ac.uk Cc: linux-arch@vger.kernel.org Cc: luc.maranget@inria.fr Cc: npiggin@gmail.com Cc: parri.andrea@gmail.com Cc: stern@rowland.harvard.edu Cc: will.deacon@arm.com Link: http://lkml.kernel.org/r/1519169112-20593-8-git-send-email-paulmck@linux.vnet.ibm.com Signed-off-by: Ingo Molnar <mingo@kernel.org>
This commit is contained in:
parent
621df431b0
commit
51de78892b
|
@ -403,7 +403,7 @@ Memory barriers come in four basic varieties:
|
||||||
where two loads are performed such that the second depends on the result
|
where two loads are performed such that the second depends on the result
|
||||||
of the first (eg: the first load retrieves the address to which the second
|
of the first (eg: the first load retrieves the address to which the second
|
||||||
load will be directed), a data dependency barrier would be required to
|
load will be directed), a data dependency barrier would be required to
|
||||||
make sure that the target of the second load is updated before the address
|
make sure that the target of the second load is updated after the address
|
||||||
obtained by the first load is accessed.
|
obtained by the first load is accessed.
|
||||||
|
|
||||||
A data dependency barrier is a partial ordering on interdependent loads
|
A data dependency barrier is a partial ordering on interdependent loads
|
||||||
|
|
Loading…
Reference in New Issue