[lkml]   [2006]   [Jul]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [patch] spinlocks: remove 'volatile'

    On Thu, 6 Jul 2006, Chris Friesen wrote:
    > The C standard requires the use of volatile for signal handlers and setjmp.

    Actually, the C standard requires "sigatomic_t".

    > For userspace at least the whole discussion of "barriers" is sort of
    > moot--there are no memory barriers defined in the C language, which makes it
    > kind of hard to write portable code that uses them.

    Any locking primitive BY DEFINITION has a barrier in it.

    If it doesn't, it's not a locking primitive, it's a random sequence of
    code that does something pointless.

    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: 2009-11-18 23:46    [W:0.021 / U:8.656 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site