[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b0df96f6-dc41-8baf-baa3-e98da94c54b7@fb.com>
Date: Sat, 5 Oct 2019 17:10:38 +0000
From: Alexei Starovoitov <ast@...com>
To: Andrii Nakryiko <andriin@...com>,
"bpf@...r.kernel.org" <bpf@...r.kernel.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"daniel@...earbox.net" <daniel@...earbox.net>
CC: "andrii.nakryiko@...il.com" <andrii.nakryiko@...il.com>,
Kernel Team <Kernel-team@...com>
Subject: Re: [PATCH bpf-next 3/3] libbpf: auto-generate list of BPF helper
definitions
On 10/5/19 12:59 AM, Andrii Nakryiko wrote:
> Get rid of list of BPF helpers in bpf_helpers.h (irony...) and
> auto-generate it into bpf_helpers_defs.h, which is now included from
> bpf_helpers.h.
>
> Suggested-by: Alexei Starovoitov<ast@...com>
> Signed-off-by: Andrii Nakryiko<andriin@...com>
> ---
> tools/lib/bpf/Makefile | 8 +-
> tools/lib/bpf/bpf_helpers.h | 264 +--
> tools/lib/bpf/bpf_helpers_defs.h | 2677 ++++++++++++++++++++++++++++++
> 3 files changed, 2685 insertions(+), 264 deletions(-)
> create mode 100644 tools/lib/bpf/bpf_helpers_defs.h
Approach looks good to me.
imo that's better than messing with macros.
Using bpf_helpers_doc.py as part of build will help man pages too.
I think we were sloppy documenting helpers, since only Quentin
was running that script regularly.
Only question is what is the reason to commit generated .h into git?
Powered by blists - more mailing lists