diff options
| author |   Yafang Shao <laoar.shao@gmail.com> | 2022-04-09 12:59:57 +0000 |
|---|---|---|
| committer |   Andrii Nakryiko <andrii@kernel.org> | 2022-04-10 20:17:16 -0700 |
| commit | a777e18f1bcd32528ff5dfd10a6629b655b05eb8 (patch) | |
| tree | 681ae396647ca9e5cb2d977f135e365d4a226c12 /tools/bpf/bpftool/map.c | |
| parent | selftests/bpf: Use libbpf 1.0 API mode instead of RLIMIT_MEMLOCK (diff) | |
| download | wireguard-linux-a777e18f1bcd32528ff5dfd10a6629b655b05eb8.tar.xz wireguard-linux-a777e18f1bcd32528ff5dfd10a6629b655b05eb8.zip | |
bpftool: Use libbpf 1.0 API mode instead of RLIMIT_MEMLOCK
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.
libbpf_set_strict_mode always return 0, so we don't need to check whether
the return value is 0 or not.
Signed-off-by: Yafang Shao <laoar.shao@gmail.com>
Signed-off-by: Andrii Nakryiko <andrii@kernel.org>
Link: https://lore.kernel.org/bpf/20220409125958.92629-4-laoar.shao@gmail.com
Diffstat (limited to 'tools/bpf/bpftool/map.c')
| -rw-r--r-- | tools/bpf/bpftool/map.c | 2 |
1 files changed, 0 insertions, 2 deletions
diff --git a/tools/bpf/bpftool/map.c b/tools/bpf/bpftool/map.c index c26378f20831..877387ef79c7 100644 --- a/tools/bpf/bpftool/map.c +++ b/tools/bpf/bpftool/map.c @@ -1342,8 +1342,6 @@ static int do_create(int argc, char **argv) goto exit; } - set_max_rlimit(); - fd = bpf_map_create(map_type, map_name, key_size, value_size, max_entries, &attr); if (fd < 0) { p_err("map create failed: %s", strerror(errno)); |