[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAADnVQLdcJMddFAxVRRaySeD06eGkU+rt0x8LkSqRak0fHqNEw@mail.gmail.com>
Date: Tue, 29 Oct 2024 08:15:12 -0700
From: Alexei Starovoitov <alexei.starovoitov@...il.com>
To: Matteo Croce <technoboy85@...il.com>
Cc: bpf <bpf@...r.kernel.org>, Alexei Starovoitov <ast@...nel.org>,
Andrii Nakryiko <andrii@...nel.org>, Daniel Borkmann <daniel@...earbox.net>,
John Fastabend <john.fastabend@...il.com>, Martin KaFai Lau <martin.lau@...ux.dev>,
Network Development <netdev@...r.kernel.org>, LKML <linux-kernel@...r.kernel.org>,
linux-trace-kernel <linux-trace-kernel@...r.kernel.org>, Matteo Croce <teknoraver@...a.com>
Subject: Re: [PATCH bpf-next v2] bpf: use kfunc hooks instead of program types
On Tue, Oct 29, 2024 at 7:34 AM Matteo Croce <technoboy85@...il.com> wrote:
>
> From: Matteo Croce <teknoraver@...a.com>
>
> Pass to register_btf_kfunc_id_set() a btf_kfunc_hook directly, instead
> of a bpf_prog_type.
> Many program types share the same kfunc hook, so some calls to
> register_btf_kfunc_id_set() can be removed.
Still nack for the same reason: let's avoid churn
when kfunc registration needs a redesign.
pw-bot: cr
Powered by blists - more mailing lists