bpf: Eliminate rlimit-based memory accounting infra for bpf maps
Remove rlimit-based accounting infrastructure code, which is not used anymore. To provide a backward compatibility, use an approximation of the bpf map memory footprint as a "memlock" value, available to a user via map info. The approximation is based on the maximal number of elements and key and value sizes. Signed-off-by:Roman Gushchin <guro@fb.com> Signed-off-by:
Alexei Starovoitov <ast@kernel.org> Acked-by:
Song Liu <songliubraving@fb.com> Link: https://lore.kernel.org/bpf/20201201215900.3569844-33-guro@fb.com
Showing
- include/linux/bpf.h 0 additions, 12 deletionsinclude/linux/bpf.h
- kernel/bpf/syscall.c 16 additions, 80 deletionskernel/bpf/syscall.c
- tools/testing/selftests/bpf/progs/bpf_iter_bpf_map.c 1 addition, 1 deletiontools/testing/selftests/bpf/progs/bpf_iter_bpf_map.c
- tools/testing/selftests/bpf/progs/map_ptr_kern.c 0 additions, 7 deletionstools/testing/selftests/bpf/progs/map_ptr_kern.c
Please register or sign in to comment