From: Lorenzo Bianconi <lorenzo@kernel.org>
To: Andrii Nakryiko <andrii.nakryiko@gmail.com>,
Alexei Starovoitov <ast@kernel.org>
Cc: "Zvi Effron" <zeffron@riotgames.com>,
"Jesper Dangaard Brouer" <brouer@redhat.com>,
"Toke Høiland-Jørgensen" <toke@redhat.com>,
"Lorenzo Bianconi" <lorenzo.bianconi@redhat.com>,
bpf <bpf@vger.kernel.org>,
"Daniel Borkmann" <daniel@iogearbox.net>,
"john fastabend" <john.fastabend@gmail.com>,
"David Ahern" <dsahern@kernel.org>,
"Eelco Chaudron" <echaudro@redhat.com>
Subject: Re: [PATCH v21 bpf-next 18/23] libbpf: Add SEC name for xdp_mb programs
Date: Wed, 26 Jan 2022 17:11:43 +0100 [thread overview]
Message-ID: <YfFyv8l6xDNM70eZ@lore-desk> (raw)
In-Reply-To: <CAEf4BzZAMtmqW4sMfhEX8WtAzmQoVQ=WupqeqXa=5KbYXAbQNA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3505 bytes --]
> On Fri, Jan 14, 2022 at 10:55 AM Zvi Effron <zeffron@riotgames.com> wrote:
> >
> > On Fri, Jan 14, 2022 at 8:50 AM Jesper Dangaard Brouer
> > <jbrouer@redhat.com> wrote:
> > >
> > >
> > >
> > > On 14/01/2022 03.09, Alexei Starovoitov wrote:
> > > > On Thu, Jan 13, 2022 at 3:58 PM Lorenzo Bianconi <lorenzo@kernel.org> wrote:
> > > >>>
> > > >>> Btw "xdp_cpumap" should be cleaned up.
> > > >>> xdp_cpumap is an attach type. It's not prog type.
> > > >>> Probably it should be "xdp/cpumap" to align with "cgroup/bind[46]" ?
> > > >>
> > > >> so for xdp "mb" or xdp "frags" it will be xdp/cpumap.mb (xdp/devmap.mb) or
> > > >> xdp/cpumap.frags (xdp/devmap.frags), right?
> > > >
> > > > xdp.frags/cpumap
> > > > xdp.frags/devmap
> > > >
> > > > The current de-facto standard for SEC("") in libbpf:
> > > > prog_type.prog_flags/attach_place
> > >
> > > Ups, did we make a mistake with SEC("xdp_devmap/")
> > >
> > > and can we correct without breaking existing programs?
> > >
> >
> > We can (at the very least) add the correct sections, even if we leave the
> > current incorrect ones as well. Ideally we'd mark the incorrect ones deprecated
> > and either remove them before libbpf 1.0 or as part of 2.0?
> >
>
> Correct, those would need to be new aliases. We can also deprecate old
> ones, if we have consensus on that. We can teach libbpf to emit
> warnings (through logs, of course) for such uses of to-be-removed
> sections aliases. We still have probably a few months before the final
> 1.0 release, should hopefully be plenty of time to people to adapt.
If we all agree on old cpumap/devmap sec deprecation and replace them with
xdp/cpumap and xdp/devmap, would it be ok something like the patch below or
would be necessary something different?
Regards,
Lorenzo
--- a/tools/lib/bpf/libbpf.c
+++ b/tools/lib/bpf/libbpf.c
@@ -6575,6 +6575,12 @@ static int libbpf_preload_prog(struct bpf_program *prog,
if (prog->type == BPF_PROG_TYPE_XDP && (def & SEC_XDP_FRAGS))
opts->prog_flags |= BPF_F_XDP_HAS_FRAGS;
+ if (strstr(prog->sec_name, "xdp_devmap") ||
+ strstr(prog->sec_name, "xdp_cpumap")) {
+ pr_warn("sec_name '%s' is deprecated, use xdp/devmap or xdp_cpumap instead\n",
+ prog->sec_name);
+ }
+
if ((prog->type == BPF_PROG_TYPE_TRACING ||
prog->type == BPF_PROG_TYPE_LSM ||
prog->type == BPF_PROG_TYPE_EXT) && !prog->attach_btf_id) {
@@ -8618,8 +8624,10 @@ static const struct bpf_sec_def section_defs[] = {
SEC_DEF("iter.s/", TRACING, BPF_TRACE_ITER, SEC_ATTACH_BTF | SEC_SLEEPABLE, attach_iter),
SEC_DEF("syscall", SYSCALL, 0, SEC_SLEEPABLE),
SEC_DEF("xdp.frags/devmap", XDP, BPF_XDP_DEVMAP, SEC_XDP_FRAGS),
+ SEC_DEF("xdp/devmap", XDP, BPF_XDP_DEVMAP, SEC_ATTACHABLE),
SEC_DEF("xdp_devmap/", XDP, BPF_XDP_DEVMAP, SEC_ATTACHABLE),
SEC_DEF("xdp.frags/cpumap", XDP, BPF_XDP_CPUMAP, SEC_XDP_FRAGS),
+ SEC_DEF("xdp/cpumap", XDP, BPF_XDP_CPUMAP, SEC_ATTACHABLE),
SEC_DEF("xdp_cpumap/", XDP, BPF_XDP_CPUMAP, SEC_ATTACHABLE),
SEC_DEF("xdp.frags", XDP, BPF_XDP, SEC_XDP_FRAGS),
SEC_DEF("xdp", XDP, BPF_XDP, SEC_ATTACHABLE_OPT | SEC_SLOPPY_PFX),
>
> > --Zvi
> >
> > > > "attach_place" is either function_name for fentry/, tp/, lsm/, etc.
> > > > or attach_type/hook/target for cgroup/bind4, cgroup_skb/egress.
> > > >
> > > > lsm.s/socket_bind -> prog_type = LSM, flags = SLEEPABLE
> > > > lsm/socket_bind -> prog_type = LSM, non sleepable.
> > > >
> > >
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2022-01-26 16:11 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-08 11:53 [PATCH v21 bpf-next 00/23] mvneta: introduce XDP multi-buffer support Lorenzo Bianconi
2022-01-08 11:53 ` [PATCH v21 bpf-next 01/23] net: skbuff: add size metadata to skb_shared_info for xdp Lorenzo Bianconi
2022-01-08 11:53 ` [PATCH v21 bpf-next 02/23] xdp: introduce flags field in xdp_buff/xdp_frame Lorenzo Bianconi
2022-01-08 11:53 ` [PATCH v21 bpf-next 03/23] net: mvneta: update mb bit before passing the xdp buffer to eBPF layer Lorenzo Bianconi
2022-01-08 11:53 ` [PATCH v21 bpf-next 04/23] net: mvneta: simplify mvneta_swbm_add_rx_fragment management Lorenzo Bianconi
2022-01-08 11:53 ` [PATCH v21 bpf-next 05/23] net: xdp: add xdp_update_skb_shared_info utility routine Lorenzo Bianconi
2022-01-08 11:53 ` [PATCH v21 bpf-next 06/23] net: marvell: rely on " Lorenzo Bianconi
2022-01-10 16:37 ` Andy Gospodarek
2022-01-11 13:05 ` Lorenzo Bianconi
2022-01-11 14:29 ` Andy Gospodarek
2022-01-08 11:53 ` [PATCH v21 bpf-next 07/23] xdp: add multi-buff support to xdp_return_{buff/frame} Lorenzo Bianconi
2022-01-08 11:53 ` [PATCH v21 bpf-next 08/23] net: mvneta: add multi buffer support to XDP_TX Lorenzo Bianconi
2022-01-08 11:53 ` [PATCH v21 bpf-next 09/23] bpf: introduce BPF_F_XDP_MB flag in prog_flags loading the ebpf program Lorenzo Bianconi
2022-01-08 11:53 ` [PATCH v21 bpf-next 10/23] net: mvneta: enable jumbo frames if the loaded XDP program support mb Lorenzo Bianconi
2022-01-08 11:53 ` [PATCH v21 bpf-next 11/23] bpf: introduce bpf_xdp_get_buff_len helper Lorenzo Bianconi
2022-01-08 11:53 ` [PATCH v21 bpf-next 12/23] bpf: add multi-buff support to the bpf_xdp_adjust_tail() API Lorenzo Bianconi
2022-01-08 11:53 ` [PATCH v21 bpf-next 13/23] bpf: add multi-buffer support to xdp copy helpers Lorenzo Bianconi
2022-01-08 11:53 ` [PATCH v21 bpf-next 14/23] bpf: move user_size out of bpf_test_init Lorenzo Bianconi
2022-01-08 11:53 ` [PATCH v21 bpf-next 15/23] bpf: introduce multibuff support to bpf_prog_test_run_xdp() Lorenzo Bianconi
2022-01-08 11:53 ` [PATCH v21 bpf-next 16/23] bpf: test_run: add xdp_shared_info pointer in bpf_test_finish signature Lorenzo Bianconi
2022-01-08 11:53 ` [PATCH v21 bpf-next 17/23] bpf: selftests: update xdp_adjust_tail selftest to include multi-buffer Lorenzo Bianconi
2022-01-08 11:53 ` [PATCH v21 bpf-next 18/23] libbpf: Add SEC name for xdp_mb programs Lorenzo Bianconi
2022-01-10 2:16 ` Andrii Nakryiko
2022-01-12 18:17 ` Lorenzo Bianconi
2022-01-12 18:24 ` Andrii Nakryiko
2022-01-12 18:35 ` Lorenzo Bianconi
2022-01-12 19:16 ` Alexei Starovoitov
2022-01-12 19:20 ` Andrii Nakryiko
2022-01-12 19:47 ` Alexei Starovoitov
2022-01-12 20:04 ` Zvi Effron
2022-01-12 20:12 ` Lorenzo Bianconi
2022-01-12 22:04 ` Toke Høiland-Jørgensen
2022-01-13 9:38 ` Jesper Dangaard Brouer
2022-01-13 10:22 ` Lorenzo Bianconi
2022-01-13 20:19 ` Alexei Starovoitov
2022-01-13 23:58 ` Lorenzo Bianconi
2022-01-14 2:09 ` Alexei Starovoitov
2022-01-14 16:50 ` Jesper Dangaard Brouer
2022-01-14 18:55 ` Zvi Effron
2022-01-14 19:36 ` Andrii Nakryiko
2022-01-26 16:11 ` Lorenzo Bianconi [this message]
2022-01-26 20:12 ` Andrii Nakryiko
2022-01-14 16:35 ` Lorenzo Bianconi
2022-01-14 19:35 ` Andrii Nakryiko
2022-01-08 11:53 ` [PATCH v21 bpf-next 19/23] bpf: generalise tail call map compatibility check Lorenzo Bianconi
2022-01-08 11:53 ` [PATCH v21 bpf-next 20/23] net: xdp: introduce bpf_xdp_pointer utility routine Lorenzo Bianconi
2022-01-08 11:53 ` [PATCH v21 bpf-next 21/23] bpf: selftests: introduce bpf_xdp_{load,store}_bytes selftest Lorenzo Bianconi
2022-01-08 11:53 ` [PATCH v21 bpf-next 22/23] bpf: selftests: add CPUMAP/DEVMAP selftests for xdp multi-buff Lorenzo Bianconi
2022-01-08 11:53 ` [PATCH v21 bpf-next 23/23] xdp: disable XDP_REDIRECT " Lorenzo Bianconi
2022-01-12 18:55 ` [PATCH v21 bpf-next 00/23] mvneta: introduce XDP multi-buffer support Lorenzo Bianconi
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=YfFyv8l6xDNM70eZ@lore-desk \
--to=lorenzo@kernel.org \
--cc=andrii.nakryiko@gmail.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=brouer@redhat.com \
--cc=daniel@iogearbox.net \
--cc=dsahern@kernel.org \
--cc=echaudro@redhat.com \
--cc=john.fastabend@gmail.com \
--cc=lorenzo.bianconi@redhat.com \
--cc=toke@redhat.com \
--cc=zeffron@riotgames.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