Searched hist:"28 b24f90020fed8e8e3e8e20575f08c1cd06e54f" (Results 1 – 6 of 6) sorted by relevance
| /linux/include/trace/events/ |
| H A D | mptcp.h | diff 28b24f90020fed8e8e3e8e20575f08c1cd06e54f Thu Sep 21 22:28:15 CEST 2023 Eric Dumazet <edumazet@google.com> net: implement lockless SO_MAX_PACING_RATE
SO_MAX_PACING_RATE setsockopt() does not need to hold
the socket lock, because sk->sk_pacing_rate readers
can run fine if the value is changed by other threads,
after adding READ_ONCE() accessors.
Signed-off-by: Eric Dumazet <edumazet@google.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
|
| /linux/net/ipv4/ |
| H A D | tcp_bbr.c | diff 28b24f90020fed8e8e3e8e20575f08c1cd06e54f Thu Sep 21 22:28:15 CEST 2023 Eric Dumazet <edumazet@google.com> net: implement lockless SO_MAX_PACING_RATE
SO_MAX_PACING_RATE setsockopt() does not need to hold
the socket lock, because sk->sk_pacing_rate readers
can run fine if the value is changed by other threads,
after adding READ_ONCE() accessors.
Signed-off-by: Eric Dumazet <edumazet@google.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
|
| H A D | tcp_output.c | diff 28b24f90020fed8e8e3e8e20575f08c1cd06e54f Thu Sep 21 22:28:15 CEST 2023 Eric Dumazet <edumazet@google.com> net: implement lockless SO_MAX_PACING_RATE
SO_MAX_PACING_RATE setsockopt() does not need to hold
the socket lock, because sk->sk_pacing_rate readers
can run fine if the value is changed by other threads,
after adding READ_ONCE() accessors.
Signed-off-by: Eric Dumazet <edumazet@google.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
|
| H A D | tcp_input.c | diff 28b24f90020fed8e8e3e8e20575f08c1cd06e54f Thu Sep 21 22:28:15 CEST 2023 Eric Dumazet <edumazet@google.com> net: implement lockless SO_MAX_PACING_RATE
SO_MAX_PACING_RATE setsockopt() does not need to hold
the socket lock, because sk->sk_pacing_rate readers
can run fine if the value is changed by other threads,
after adding READ_ONCE() accessors.
Signed-off-by: Eric Dumazet <edumazet@google.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
|
| /linux/net/sched/ |
| H A D | sch_fq.c | diff 28b24f90020fed8e8e3e8e20575f08c1cd06e54f Thu Sep 21 22:28:15 CEST 2023 Eric Dumazet <edumazet@google.com> net: implement lockless SO_MAX_PACING_RATE
SO_MAX_PACING_RATE setsockopt() does not need to hold
the socket lock, because sk->sk_pacing_rate readers
can run fine if the value is changed by other threads,
after adding READ_ONCE() accessors.
Signed-off-by: Eric Dumazet <edumazet@google.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
|
| /linux/net/core/ |
| H A D | sock.c | diff 28b24f90020fed8e8e3e8e20575f08c1cd06e54f Thu Sep 21 22:28:15 CEST 2023 Eric Dumazet <edumazet@google.com> net: implement lockless SO_MAX_PACING_RATE
SO_MAX_PACING_RATE setsockopt() does not need to hold
the socket lock, because sk->sk_pacing_rate readers
can run fine if the value is changed by other threads,
after adding READ_ONCE() accessors.
Signed-off-by: Eric Dumazet <edumazet@google.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
|