[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87o7qphspq.fsf@meer.lwn.net>
Date: Mon, 23 Jan 2023 14:00:17 -0700
From: Jonathan Corbet <corbet@....net>
To: Daniel Borkmann <daniel@...earbox.net>,
Alexei Starovoitov <alexei.starovoitov@...il.com>,
David Vernet <void@...ifault.com>
Cc: bpf@...r.kernel.org, ast@...nel.org, andrii@...nel.org,
martin.lau@...ux.dev, song@...nel.org, yhs@...a.com,
john.fastabend@...il.com, kpsingh@...nel.org, sdf@...gle.com,
haoluo@...gle.com, jolsa@...nel.org, linux-kernel@...r.kernel.org,
kernel-team@...a.com, memxor@...il.com
Subject: Re: [PATCH bpf-next v2 3/3] bpf: Use BPF_KFUNC macro at all kfunc
definitions
Daniel Borkmann <daniel@...earbox.net> writes:
> Did you look into making this similar to the EXPORT_SYMBOL() infra? If possible
> that would look much more natural to developers, e.g. :
>
> struct nf_conn *
> bpf_skb_ct_lookup(struct __sk_buff *skb_ctx, struct bpf_sock_tuple *bpf_tuple,
> u32 tuple__sz, struct bpf_ct_opts *opts, u32 opts__sz)
> {
> [...]
> }
>
> EXPORT_BPF_KFUNC(bpf_skb_ct_lookup);
That was my question too; it's a similar functionality that would be
nice to express in a similar way. Even better, if possible, might be to
fold it into BTF_ID_FLAGS, which I might then rename to EXPORT_KFUNC()
or some such ... :)
Thanks,
jon
Powered by blists - more mailing lists