alan-maguire
commented
3 weeks ago the first thing to note above is
bpftune[38936]: bpftune works, but no BPF Type Format information (BTF) is available. This means kernel data structure of fsets may not match those at compile-time, and tuners may not operate as expected. This mode of operation is unsupported, and failures are expected , so be warned.
Can you check if /sys/kernel/btf/vmlinux is present? If not this makes bpftune operation difficult since it's relying on compiled-in offsets. In the absence of BTF we can get weird results like the tcp buffer rmem values above.
andrey-admin
Hello,
Trying run bpftune on google instance on 6.5.0-1022-gcp kernel. Got this on logs:
Jun 14 11:58:59 nginx-08 bpftune[38936]: bpftune works, but no BPF Type Format information (BTF) is available. This means kernel data structure of fsets may not match those at compile-time, and tuners may not operate as expected. This mode of operation is unsupported, and failures are expected , so be warned. Jun 14 11:58:59 nginx-08 bpftune[38936]: bpftune supports per-netns policy (via netns cookie) Jun 14 11:58:59 nginx-08 bpftune[38936]: could not load skeleton: Kernel verifier blocks program loading Jun 14 11:58:59 nginx-08 bpftune[38936]: error initializing '/usr/lib64/bpftune//tcp_conn_tuner.so: Unknown error 4007 Jun 14 11:58:59 nginx-08 bpftune[38936]: could not open /proc/sys/net/ipv6/neigh/default/gc_interval (netns fd 0) for reading: No such file or directory Jun 14 11:58:59 nginx-08 bpftune[38936]: could not open /proc/sys/net/ipv6/neigh/default/gc_stale_time (netns fd 0) for reading: No such file or directory Jun 14 11:58:59 nginx-08 bpftune[38936]: could not open /proc/sys/net/ipv6/neigh/default/gc_thresh1 (netns fd 0) for reading: No such file or directory Jun 14 11:58:59 nginx-08 bpftune[38936]: could not open /proc/sys/net/ipv6/neigh/default/gc_thresh2 (netns fd 0) for reading: No such file or directory Jun 14 11:58:59 nginx-08 bpftune[38936]: could not open /proc/sys/net/ipv6/neigh/default/gc_thresh3 (netns fd 0) for reading: No such file or directory Jun 14 11:59:00 nginx-08 bpftune[38936]: could not open /proc/sys/net/ipv6/route/max_size (netns fd 0) for reading: No such file or directory Jun 14 11:59:00 nginx-08 bpftune[38936]: could not open /proc/sys/net/ipv6/ip6frag_high_thresh (netns fd 0) for reading: No such file or directory Jun 14 11:59:00 nginx-08 bpftune[38936]: Scenario 'need to increase TCP buffer size(s)' occurred for tunable 'net.ipv4.tcp_rmem' in global ns. Need to increase buffer size(s) to maximize throughput Jun 14 11:59:00 nginx-08 bpftune[38936]: Due to need to increase max buffer size to maximize throughput change net.ipv4.tcp_rmem(min default max) from (16777217 0 300) -> (16777217 0 375) Jun 14 11:59:00 nginx-08 bpftune[38936]: Scenario 'need to increase TCP buffer size(s)' occurred for tunable 'net.ipv4.tcp_rmem' in global ns. Need to increase buffer size(s) to maximize throughput Jun 14 11:59:00 nginx-08 bpftune[38936]: Due to need to increase max buffer size to maximize throughput change net.ipv4.tcp_rmem(min default max) from (16777217 0 300) -> (16777217 0 375) Jun 14 11:59:00 nginx-08 bpftune[38936]: Scenario 'need to increase TCP buffer size(s)' occurred for tunable 'net.ipv4.tcp_rmem' in global ns. Need to increase buffer size(s) to maximize throughput Jun 14 11:59:00 nginx-08 bpftune[38936]: Due to need to increase max buffer size to maximize throughput change net.ipv4.tcp_rmem(min default max) from (16777217 0 300) -> (16777217 0 375) Jun 14 11:59:00 nginx-08 bpftune[38936]: Scenario 'need to increase TCP buffer size(s)' occurred for tunable 'net.ipv4.tcp_rmem' in global ns. Need to increase buffer size(s) to maximize throughput Jun 14 11:59:00 nginx-08 bpftune[38936]: Due to need to increase max buffer size to maximize throughput change net.ipv4.tcp_rmem(min default max) from (16777217 0 300) -> (16777217 0 375)
How that can be fixed?
Thanks!