[lkml]   [2004]   [Jul]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH] Fix the cpumask rewrite

> 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)

64 bytes from 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
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 14:04    [W:0.145 / U:0.036 seconds]
©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site