Hello:
This series was applied to bpf/bpf-next.git (master) by Andrii Nakryiko andrii@kernel.org:
On Sat, 9 Apr 2022 12:59:54 +0000 you wrote:
We have switched to memcg-based memory accouting and thus the rlimit is not needed any more. LIBBPF_STRICT_AUTO_RLIMIT_MEMLOCK was introduced in libbpf for backward compatibility, so we can use it instead now.
This patchset cleanups the usage of RLIMIT_MEMLOCK in tools/bpf/, tools/testing/selftests/bpf and samples/bpf. The file tools/testing/selftests/bpf/bpf_rlimit.h is removed. The included header sys/resource.h is removed from many files as it is useless in these files.
[...]
Here is the summary with links: - [bpf-next,v4,1/4] samples/bpf: Use libbpf 1.0 API mode instead of RLIMIT_MEMLOCK https://git.kernel.org/bpf/bpf-next/c/b25acdafd373 - [bpf-next,v4,2/4] selftests/bpf: Use libbpf 1.0 API mode instead of RLIMIT_MEMLOCK https://git.kernel.org/bpf/bpf-next/c/b858ba8c52b6 - [bpf-next,v4,3/4] bpftool: Use libbpf 1.0 API mode instead of RLIMIT_MEMLOCK https://git.kernel.org/bpf/bpf-next/c/a777e18f1bcd - [bpf-next,v4,4/4] tools/runqslower: Use libbpf 1.0 API mode instead of RLIMIT_MEMLOCK https://git.kernel.org/bpf/bpf-next/c/451b5fbc2c56
You are awesome, thank you!