Re: [PATCH bpf-next v5 05/11] bpf: Adds field bpf_sock_ops_flags to tcp_sock

2018-01-09 Thread Lawrence Brakmo
On 1/9/18, 3:31 PM, "Eric Dumazet" wrote: On Tue, 2018-01-09 at 13:06 -0800, Lawrence Brakmo wrote: > Adds field bpf_sock_ops_flags to tcp_sock and bpf_sock_ops. Its primary > use is to determine if there should be calls to sock_ops bpf program at > various points in the TCP code.

Re: [PATCH bpf-next v5 05/11] bpf: Adds field bpf_sock_ops_flags to tcp_sock

2018-01-09 Thread Eric Dumazet
On Tue, 2018-01-09 at 13:06 -0800, Lawrence Brakmo wrote: > Adds field bpf_sock_ops_flags to tcp_sock and bpf_sock_ops. Its primary > use is to determine if there should be calls to sock_ops bpf program at > various points in the TCP code. The field is initialized to zero, > disabling the calls. A

[PATCH bpf-next v5 05/11] bpf: Adds field bpf_sock_ops_flags to tcp_sock

2018-01-09 Thread Lawrence Brakmo
Adds field bpf_sock_ops_flags to tcp_sock and bpf_sock_ops. Its primary use is to determine if there should be calls to sock_ops bpf program at various points in the TCP code. The field is initialized to zero, disabling the calls. A sock_ops BPF program can set, per connection and as necessary, whe