bpf.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexei Starovoitov <alexei.starovoitov@gmail.com>
To: Andrii Nakryiko <andriin@fb.com>
Cc: bpf <bpf@vger.kernel.org>,
	Network Development <netdev@vger.kernel.org>,
	Alexei Starovoitov <ast@fb.com>,
	Daniel Borkmann <daniel@iogearbox.net>,
	Quentin Monnet <quentin.monnet@netronome.com>,
	Andrii Nakryiko <andrii.nakryiko@gmail.com>,
	Kernel Team <kernel-team@fb.com>
Subject: Re: [PATCH v4 bpf-next 0/3] Auto-generate list of BPF helpers
Date: Sun, 6 Oct 2019 22:35:17 -0700	[thread overview]
Message-ID: <CAADnVQK=Pc6Z5q7=oF1xdxq3ThX-Ox5mjmVk3DkwqUrXRHZ1Xg@mail.gmail.com> (raw)
In-Reply-To: <20191007030738.2627420-1-andriin@fb.com>

On Sun, Oct 6, 2019 at 8:08 PM Andrii Nakryiko <andriin@fb.com> wrote:
>
> This patch set adds ability to auto-generate list of BPF helper definitions.
> It relies on existing scripts/bpf_helpers_doc.py and include/uapi/linux/bpf.h
> having a well-defined set of comments. bpf_helper_defs.h contains all BPF
> helper signatures which stay in sync with latest bpf.h UAPI. This
> auto-generated header is included from bpf_helpers.h, while all previously
> hand-written BPF helper definitions are simultaneously removed in patch #3.
> The end result is less manually maintained and redundant boilerplate code,
> while also more consistent and well-documented set of BPF helpers. Generated
> helper definitions are completely independent from a specific bpf.h on
> a target system, because it doesn't use BPF_FUNC_xxx enums.

Applied. Thanks

      parent reply	other threads:[~2019-10-07  5:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-07  3:07 [PATCH v4 bpf-next 0/3] Auto-generate list of BPF helpers Andrii Nakryiko
2019-10-07  3:07 ` [PATCH v4 bpf-next 1/3] uapi/bpf: fix helper docs Andrii Nakryiko
2019-10-07  9:43   ` Daniel Borkmann
2019-10-07 17:47     ` Andrii Nakryiko
2019-10-08 21:49       ` Daniel Borkmann
2019-10-08 23:32         ` Andrii Nakryiko
2019-10-10 23:55           ` Daniel Borkmann
2019-10-07  3:07 ` [PATCH v4 bpf-next 2/3] scripts/bpf: teach bpf_helpers_doc.py to dump BPF helper definitions Andrii Nakryiko
2019-10-07  3:07 ` [PATCH v4 bpf-next 3/3] libbpf: auto-generate list of " Andrii Nakryiko
2019-10-07  5:35 ` Alexei Starovoitov [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAADnVQK=Pc6Z5q7=oF1xdxq3ThX-Ox5mjmVk3DkwqUrXRHZ1Xg@mail.gmail.com' \
    --to=alexei.starovoitov@gmail.com \
    --cc=andrii.nakryiko@gmail.com \
    --cc=andriin@fb.com \
    --cc=ast@fb.com \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=kernel-team@fb.com \
    --cc=netdev@vger.kernel.org \
    --cc=quentin.monnet@netronome.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).