On Mon, Oct 09, 2017 at 07:28:45PM +0100, Mark Rutland wrote:
> - ACCESS_ONCE(sk->sk_pacing_rate) = min_t(u64, rate,
> - sk->sk_max_pacing_rate);
> + WRITE_ONCE(sk->sk_pacing_rate) = min_t(u64, rate,
> +
On Mon, Oct 09, 2017 at 07:28:45PM +0100, Mark Rutland wrote:
> - ACCESS_ONCE(sk->sk_pacing_rate) = min_t(u64, rate,
> - sk->sk_max_pacing_rate);
> + WRITE_ONCE(sk->sk_pacing_rate) = min_t(u64, rate,
> +
For several reasons, it is desirable to use {READ,WRITE}_ONCE() in
preference to ACCESS_ONCE(), and new code is expected to use one of the
former. So far, there's been no reason to change most existing uses of
ACCESS_ONCE(), as these aren't currently harmful.
However, for some features it is
For several reasons, it is desirable to use {READ,WRITE}_ONCE() in
preference to ACCESS_ONCE(), and new code is expected to use one of the
former. So far, there's been no reason to change most existing uses of
ACCESS_ONCE(), as these aren't currently harmful.
However, for some features it is
4 matches
Mail list logo
