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
This commit is contained in:
committed by
Andrii Nakryiko
parent
b858ba8c52
commit
a777e18f1b
@@ -1604,8 +1604,6 @@ static int load_with_options(int argc, char **argv, bool first_prog_only)
|
||||
}
|
||||
}
|
||||
|
||||
set_max_rlimit();
|
||||
|
||||
if (verifier_logs)
|
||||
/* log_level1 + log_level2 + stats, but not stable UAPI */
|
||||
open_opts.kernel_log_level = 1 + 2 + 4;
|
||||
@@ -2303,7 +2301,6 @@ static int do_profile(int argc, char **argv)
|
||||
}
|
||||
}
|
||||
|
||||
set_max_rlimit();
|
||||
err = profiler_bpf__load(profile_obj);
|
||||
if (err) {
|
||||
p_err("failed to load profile_obj");
|
||||
|
||||
Reference in New Issue
Block a user