[lkml]   [2006]   [Mar]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH] Document Linux's memory barriers
    Duncan Sands writes:

    > On UP you at least need compiler barriers, right? You're in trouble if you think
    > you are writing in a certain order, and expect to see the same order from an
    > interrupt handler, but the compiler decided to rearrange the order of the writes...

    I'd be interested to know what the C standard says about whether the
    compiler can reorder writes that may be visible to a signal handler.
    An interrupt handler in the kernel is logically equivalent to a signal
    handler in normal C code.

    Surely there are some C language lawyers on one of the lists that this
    thread is going to?

    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: 2006-03-08 23:14    [W:0.018 / U:4.952 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site