[lkml]   [2007]   [Aug]   [15]   [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
    Chris Snook <> wrote:
    > Because atomic operations are generally used for synchronization, which requires
    > volatile behavior. Most such codepaths currently use an inefficient barrier().
    > Some forget to and we get bugs, because people assume that atomic_read()
    > actually reads something, and atomic_write() actually writes something. Worse,
    > these are architecture-specific, even compiler version-specific bugs that are
    > often difficult to track down.

    I'm yet to see a single example from the current tree where
    this patch series is the correct solution. So far the only
    example has been a buggy piece of code which has since been
    fixed with a cpu_relax.

    Visit Openswan at
    Email: Herbert Xu ~{PmV>HI~} <>
    Home Page:
    PGP Key:
    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 08:53    [W:0.020 / U:7.872 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site