diff options
| author | Andrii Nakryiko <andrii@kernel.org> | 2022-01-24 11:42:49 -0800 |
|---|---|---|
| committer | Alexei Starovoitov <ast@kernel.org> | 2022-01-25 17:59:06 -0800 |
| commit | c5023b8f2693035d7ce2cf8153298002182049ff (patch) | |
| tree | 609565a4cae4d2ac2e43712aed02f95003dcaab0 /tools/testing/selftests/bpf/prog_tests/get_stackid_cannot_attach.c | |
| parent | 20eccf29e2979a18411517061998bac7d12c8543 (diff) | |
| download | linux-c5023b8f2693035d7ce2cf8153298002182049ff.tar.bz2 | |
libbpf: deprecate bpf_map__resize()
Deprecated bpf_map__resize() in favor of bpf_map__set_max_entries()
setter. In addition to having a surprising name (users often don't
realize that they need to use bpf_map__resize()), the name also implies
some magic way of resizing BPF map after it is created, which is clearly
not the case.
Another minor annoyance is that bpf_map__resize() disallows 0 value for
max_entries, which in some cases is totally acceptable (e.g., like for
BPF perf buf case to let libbpf auto-create one buffer per each
available CPU core).
[0] Closes: https://github.com/libbpf/libbpf/issues/304
Signed-off-by: Andrii Nakryiko <andrii@kernel.org>
Link: https://lore.kernel.org/r/20220124194254.2051434-3-andrii@kernel.org
Signed-off-by: Alexei Starovoitov <ast@kernel.org>
Diffstat (limited to 'tools/testing/selftests/bpf/prog_tests/get_stackid_cannot_attach.c')
0 files changed, 0 insertions, 0 deletions