lkml.org 
[lkml]   [2004]   [Jul]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [PATCH] Fix the cpumask rewrite
    Hi!

    > And the same is true of "volatile" for the bitop functions. They are
    > volatile not because they require the data to be volatile, but because
    > they have at least traditionally been used for various cases, _including_
    > volatile.
    >
    > Now, we could say that we don't do that any more, and decide that the
    > regular bitop functions really cannot be used on volatile stuff. But
    > that's a BIG decision. And it's certainly not a decision that parisc
    > users should make.

    Heh, with vojtech we introduced locking into input layer
    (there was none before)... using test_bit/set_bit.

    (I just hope set_bit etc implies memory barrier... or we'll have to do
    it once more)

    Pavel
    --
    64 bytes from 195.113.31.123: icmp_seq=28 ttl=51 time=448769.1 ms

    -
    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: 2005-03-22 14:04    [W:0.021 / U:0.352 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site