lkml.org 
[lkml]   [2018]   [Feb]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    Patch in this message
    /
    From
    Subject[PATCH RFC tools/lkmm 08/12] memory-barriers: Fix description of data dependency barriers
    Date
    From: Nikolay Borisov <nborisov@suse.com>

    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>
    ---
    Documentation/memory-barriers.txt | 2 +-
    1 file changed, 1 insertion(+), 1 deletion(-)

    diff --git a/Documentation/memory-barriers.txt b/Documentation/memory-barriers.txt
    index 74ad222d11ed..0d83333b84a9 100644
    --- a/Documentation/memory-barriers.txt
    +++ b/Documentation/memory-barriers.txt
    @@ -400,7 +400,7 @@ Memory barriers come in four basic varieties:
    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
    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.

    A data dependency barrier is a partial ordering on interdependent loads
    --
    2.5.2
    \
     
     \ /
      Last update: 2018-02-21 00:28    [W:4.588 / U:0.008 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site