lkml.org 
[lkml]   [2007]   [Aug]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    From
    SubjectRe: [PATCH 0/24] make atomic_read() behave consistently across all architectures
    Date
    > I'd go so far as to say that anywhere where you want a non-"volatile"
    > atomic_read, either your code is buggy, or else an int would work just
    > as well.

    Even, the only way to implement a "non-volatile" atomic_read() is
    essentially as a plain int (you can do some tricks so you cannot
    assign to the result and stuff like that, but that's not the issue
    here).

    So if that would be the behaviour we wanted, just get rid of that
    whole atomic_read() thing, so no one can misuse it anymore.


    Segher

    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2007-08-16 21:55    [W:4.218 / U:0.364 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site