diff options
author | Antoine Tenart <atenart@kernel.org> | 2024-06-24 11:09:07 +0200 |
---|---|---|
committer | Andrii Nakryiko <andrii@kernel.org> | 2024-06-24 09:19:42 -0700 |
commit | c73a9683cb21012b6c0f14217974837151c527a8 (patch) | |
tree | f5de59085d4b706dd8324c7167e9a9df7fefae03 /COPYING | |
parent | 5a532459aa919d055d822d8db4ea2c5c8d511568 (diff) | |
download | linux-c73a9683cb21012b6c0f14217974837151c527a8.tar.gz linux-c73a9683cb21012b6c0f14217974837151c527a8.tar.bz2 linux-c73a9683cb21012b6c0f14217974837151c527a8.zip |
libbpf: Skip base btf sanity checks
When upgrading to libbpf 1.3 we noticed a big performance hit while
loading programs using CORE on non base-BTF symbols. This was tracked
down to the new BTF sanity check logic. The issue is the base BTF
definitions are checked first for the base BTF and then again for every
module BTF.
Loading 5 dummy programs (using libbpf-rs) that are using CORE on a
non-base BTF symbol on my system:
- Before this fix: 3s.
- With this fix: 0.1s.
Fix this by only checking the types starting at the BTF start id. This
should ensure the base BTF is still checked as expected but only once
(btf->start_id == 1 when creating the base BTF), and then only
additional types are checked for each module BTF.
Fixes: 3903802bb99a ("libbpf: Add basic BTF sanity validation")
Signed-off-by: Antoine Tenart <atenart@kernel.org>
Signed-off-by: Andrii Nakryiko <andrii@kernel.org>
Reviewed-by: Alan Maguire <alan.maguire@oracle.com>
Link: https://lore.kernel.org/bpf/20240624090908.171231-1-atenart@kernel.org
Diffstat (limited to 'COPYING')
0 files changed, 0 insertions, 0 deletions