[lkml]   [2007]   [Aug]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH 0/24] make atomic_read() behave consistently across all architectures
    On Thu, 9 Aug 2007, Chris Snook wrote:

    > This patchset makes the behavior of atomic_read uniform by removing the
    > volatile keyword from all atomic_t and atomic64_t definitions that currently
    > have it, and instead explicitly casts the variable as volatile in
    > atomic_read(). This leaves little room for creative optimization by the
    > compiler, and is in keeping with the principles behind "volatile considered
    > harmful".

    volatile is generally harmful even in atomic_read(). Barriers control
    visibility and AFAICT things are fine.
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2007-08-15 00:35    [W:0.022 / U:161.392 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site