diff options
author | 2022-03-11 12:11:35 -0800 | |
---|---|---|
committer | 2022-03-20 19:07:14 -0700 | |
commit | ef078600eec20f20eb7833cf597d4a5edf2953c1 (patch) | |
tree | 0aeb39efa44e717abe934c9ccdbd68459b337471 /tools/perf/scripts/python/export-to-postgresql.py | |
parent | Merge branch 'Make 2-byte access to bpf_sk_lookup->remote_port endian-agnostic' (diff) | |
download | linux-dev-ef078600eec20f20eb7833cf597d4a5edf2953c1.tar.xz linux-dev-ef078600eec20f20eb7833cf597d4a5edf2953c1.zip |
bpf: Select proper size for bpf_prog_pack
Using HPAGE_PMD_SIZE as the size for bpf_prog_pack is not ideal in some
cases. Specifically, for NUMA systems, __vmalloc_node_range requires
PMD_SIZE * num_online_nodes() to allocate huge pages. Also, if the system
does not support huge pages (i.e., with cmdline option nohugevmalloc), it
is better to use PAGE_SIZE packs.
Add logic to select proper size for bpf_prog_pack. This solution is not
ideal, as it makes assumption about the behavior of module_alloc and
__vmalloc_node_range. However, it appears to be the easiest solution as
it doesn't require changes in module_alloc and vmalloc code.
Fixes: 57631054fae6 ("bpf: Introduce bpf_prog_pack allocator")
Signed-off-by: Song Liu <song@kernel.org>
Signed-off-by: Alexei Starovoitov <ast@kernel.org>
Link: https://lore.kernel.org/bpf/20220311201135.3573610-1-song@kernel.org
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions