[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
    Herbert Xu wrote:

    > But I have to say that I still don't know of a single place
    > where one would actually use the volatile variant.

    Given that many of the existing users do currently have "volatile", are
    you comfortable simply removing that behaviour from them? Are you sure
    that you will not introduce any issues?

    Forcing a re-read is only a performance penalty. Removing it can cause
    behavioural changes.

    I would be more comfortable making the default match the majority of the
    current implementations (ie: volatile semantics). Then, if someone
    cares about performance they can explicitly validate the call path and
    convert it over to the non-volatile version.

    Correctness before speed...

    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-16 04:27    [W:0.020 / U:5.932 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site