Lines Matching refs:be

1 Why the "volatile" type class should not be used
4 C programmers have often taken volatile to mean that the variable could be
20 unwanted optimization.  If they are being used properly, there will be no
34 want to play with that data will be waiting on the lock.  The spinlock
36 meaning that data accesses will not be optimized across them.  So the
37 compiler might think it knows what will be in shared_data, but the
39 forget anything it knows.  There will be no optimization problems with
42 If shared_data were declared volatile, the locking would still be
43 necessary.  But the compiler would also be prevented from optimizing access
45 can be working with it.  While the lock is held, shared_data is not
50 registers.  Within the kernel, register accesses, too, should be protected
58 Another situation where one might be tempted to use volatile is
83     every time it is referenced, but it can be read without any special
84     locking.  So jiffies can be volatile, but the addition of other
86     to be a "stupid legacy" issue (Linus's words) in this regard; fixing it
87     would be more trouble than it is worth.
89   - Pointers to data structures in coherent memory which might be modified
90     by I/O devices can, sometimes, legitimately be volatile.  A ring buffer
96 result, the use of volatile is likely to be seen as a bug and will bring