[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAGqxgpvC2W24NGTVBoxSgcsifw=_6kbv6wOagHva9LUZyDjOjw@mail.gmail.com>
Date: Fri, 29 Oct 2021 02:51:16 -0300
From: Rafael David Tinoco <rafaeldtinoco@...il.com>
To: Alexei Starovoitov <alexei.starovoitov@...il.com>
Cc: Mauricio Vásquez <mauricio@...volk.io>,
Network Development <netdev@...r.kernel.org>,
bpf <bpf@...r.kernel.org>, Alexei Starovoitov <ast@...nel.org>,
Daniel Borkmann <daniel@...earbox.net>,
Andrii Nakryiko <andrii@...nel.org>
Subject: Re: [PATCH bpf-next 0/2] libbpf: Implement BTF Generator API
> > Have you considered generating kernel BTF with fields that are accessed
> > by bpf prog only and replacing all other fields with padding ?
>
> That is exactly the result of our final BTF file. We only include the
> fields and types being used by the given eBPF object:
A full explanation on this here:
https://github.com/aquasecurity/btfhub/tree/main/tools#how-to-use-libbpf-co-re-relocations-to-build-a-btf-file
Powered by blists - more mailing lists