lkml.org 
[lkml]   [2021]   [Oct]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    Subjectdata dependency naming inconsistency
    Hello Paul, all!
    I've been reading with interest Paul's posts about Rust interactions with LKMM
    https://paulmck.livejournal.com/63316.html
    and in particular it states:
    A data dependency involves a load whose return value directly or
    indirectly determine the value stored by a later store, which results in
    the load being ordered before the store.

    This matches the perf book:
    A data dependency occurs when the value returned by
    a load instruction is used to compute the data stored by
    a later store instruction.

    however, memory-barriers.txt states:

    A data dependency barrier is a partial ordering on interdependent loads
    only; it is not required to have any effect on stores, independent loads
    or overlapping loads.

    It also says:
    A data-dependency barrier is not required to order dependent writes
    because the CPUs that the Linux kernel supports don't do writes
    until they are certain (1) that the write will actually happen, (2)
    of the location of the write, and (3) of the value to be written.

    so the result it the same: writes are ordered without a barrier,
    reads are ordered by a barrier.

    However, it would seem that a bit more consistency in naming won't
    hurt.

    Thanks,

    --
    MST

    \
     
     \ /
      Last update: 2021-10-11 13:07    [W:3.981 / U:0.360 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site