aboutsummaryrefslogtreecommitdiffstats
path: root/include/net
diff options
context:
space:
mode:
authorAndrii Nakryiko <andrii@kernel.org>2021-10-01 15:31:51 -0700
committerAndrii Nakryiko <andrii@kernel.org>2021-10-01 15:31:51 -0700
commitd636c8da2d60cc4841ebd7b6e6a02db5c33e11e4 (patch)
tree99c4e3b27c85b415115fb1f648e7d663d4f1f669 /include/net
parentbpf/tests: Add test of LDX_MEM with operand aliasing (diff)
parentselftests/bpf: Use BTF-defined key/value for map definitions (diff)
downloadlinux-dev-d636c8da2d60cc4841ebd7b6e6a02db5c33e11e4.tar.xz
linux-dev-d636c8da2d60cc4841ebd7b6e6a02db5c33e11e4.zip
Merge branch 'libbpf: Support uniform BTF-defined key/value specification across all BPF maps'
Hengqi Chen says: ==================== Currently a bunch of (usually pretty specialized) BPF maps do not support specifying BTF types for they key and value. For such maps, specifying their definition like this: struct { __uint(type, BPF_MAP_TYPE_PERF_EVENT_ARRAY); __type(key, int); __type(value, int); } my_perf_buf SEC(".maps"); Would actually produce warnings about retrying BPF map creation without BTF. Users are forced to know such nuances and use __uint(key_size, 4) instead. This is non-uniform, annoying, and inconvenient. This patch set teaches libbpf to recognize those specialized maps and removes BTF type IDs when creating BPF map. Also, update existing BPF selftests to exericse this change. ==================== Signed-off-by: Andrii Nakryiko <andrii@kernel.org>
Diffstat (limited to 'include/net')
0 files changed, 0 insertions, 0 deletions