On 09/26/16 01:55, Peter Zijlstra wrote:
On Sun, Sep 25, 2016 at 07:08:45PM -0700, Bart Van Assche wrote:
A quote from Documentation/memory_barriers.txt:
For example, because 'jiffies' is marked volatile, it is never
necessary to say READ_ONCE(jiffies). The reason for this is
that READ_ONCE()
On 09/26/16 01:55, Peter Zijlstra wrote:
On Sun, Sep 25, 2016 at 07:08:45PM -0700, Bart Van Assche wrote:
A quote from Documentation/memory_barriers.txt:
For example, because 'jiffies' is marked volatile, it is never
necessary to say READ_ONCE(jiffies). The reason for this is
that READ_ONCE()
On Sun, Sep 25, 2016 at 07:08:45PM -0700, Bart Van Assche wrote:
> A quote from Documentation/memory_barriers.txt:
>
> For example, because 'jiffies' is marked volatile, it is never
> necessary to say READ_ONCE(jiffies). The reason for this is
> that READ_ONCE() and WRITE_ONCE() are implemented
On Sun, Sep 25, 2016 at 07:08:45PM -0700, Bart Van Assche wrote:
> A quote from Documentation/memory_barriers.txt:
>
> For example, because 'jiffies' is marked volatile, it is never
> necessary to say READ_ONCE(jiffies). The reason for this is
> that READ_ONCE() and WRITE_ONCE() are implemented
A quote from Documentation/memory_barriers.txt:
For example, because 'jiffies' is marked volatile, it is never
necessary to say READ_ONCE(jiffies). The reason for this is
that READ_ONCE() and WRITE_ONCE() are implemented as volatile
casts, which has no effect when its argument is already marked
A quote from Documentation/memory_barriers.txt:
For example, because 'jiffies' is marked volatile, it is never
necessary to say READ_ONCE(jiffies). The reason for this is
that READ_ONCE() and WRITE_ONCE() are implemented as volatile
casts, which has no effect when its argument is already marked
6 matches
Mail list logo
