From: Andrii Nakryiko <andrii.nakryiko@gmail.com>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: "Lorenzo Bianconi" <lorenzo@kernel.org>,
"Andrii Nakryiko" <andrii@kernel.org>, bpf <bpf@vger.kernel.org>,
"Network Development" <netdev@vger.kernel.org>,
"Lorenzo Bianconi" <lorenzo.bianconi@redhat.com>,
"David S. Miller" <davem@davemloft.net>,
"Jakub Kicinski" <kuba@kernel.org>,
"Alexei Starovoitov" <ast@kernel.org>,
"Daniel Borkmann" <daniel@iogearbox.net>,
"Shay Agroskin" <shayagr@amazon.com>,
"John Fastabend" <john.fastabend@gmail.com>,
"David Ahern" <dsahern@kernel.org>,
"Jesper Dangaard Brouer" <brouer@redhat.com>,
"Eelco Chaudron" <echaudro@redhat.com>,
"Jason Wang" <jasowang@redhat.com>,
"Alexander Duyck" <alexander.duyck@gmail.com>,
"Saeed Mahameed" <saeed@kernel.org>,
"Fijalkowski, Maciej" <maciej.fijalkowski@intel.com>,
"Karlsson, Magnus" <magnus.karlsson@intel.com>,
tirthendu.sarkar@intel.com,
"Toke Høiland-Jørgensen" <toke@redhat.com>
Subject: Re: [PATCH v22 bpf-next 18/23] libbpf: Add SEC name for xdp multi-frags programs
Date: Tue, 18 Jan 2022 17:11:15 -0800 [thread overview]
Message-ID: <CAEf4BzYHyCz5QNwuuKnRRrqCTcP0c0Q6fdi0N5_Yp8yNXvxReQ@mail.gmail.com> (raw)
In-Reply-To: <CAADnVQJgKVQ8vNfiazTcNbZVFTb2x=7G1WUda7O+LHM8Hs=KCw@mail.gmail.com>
On Tue, Jan 18, 2022 at 2:33 PM Alexei Starovoitov
<alexei.starovoitov@gmail.com> wrote:
>
> On Tue, Jan 18, 2022 at 2:31 PM Lorenzo Bianconi <lorenzo@kernel.org> wrote:
> >
> > > On Mon, Jan 17, 2022 at 06:28:30PM +0100, Lorenzo Bianconi wrote:
> > > > Introduce support for the following SEC entries for XDP multi-frags
> > > > property:
> > > > - SEC("xdp.frags")
> > > > - SEC("xdp.frags/devmap")
> > > > - SEC("xdp.frags/cpumap")
> > > >
> > > > Acked-by: Toke Hoiland-Jorgensen <toke@redhat.com>
> > > > Acked-by: John Fastabend <john.fastabend@gmail.com>
> > > > Signed-off-by: Lorenzo Bianconi <lorenzo@kernel.org>
> > > > ---
> > > > tools/lib/bpf/libbpf.c | 6 ++++++
> > > > 1 file changed, 6 insertions(+)
> > > >
> > > > diff --git a/tools/lib/bpf/libbpf.c b/tools/lib/bpf/libbpf.c
> > > > index fdb3536afa7d..611e81357fb6 100644
> > > > --- a/tools/lib/bpf/libbpf.c
> > > > +++ b/tools/lib/bpf/libbpf.c
> > > > @@ -6562,6 +6562,9 @@ static int libbpf_preload_prog(struct bpf_program *prog,
> > > > if (def & SEC_SLEEPABLE)
> > > > opts->prog_flags |= BPF_F_SLEEPABLE;
> > > >
> > > > + if (prog->type == BPF_PROG_TYPE_XDP && strstr(prog->sec_name, ".frags"))
> > > > + opts->prog_flags |= BPF_F_XDP_HAS_FRAGS;
> > >
> > > That's a bit sloppy.
> > > Could you handle it similar to SEC_SLEEPABLE?
> > >
> > > > +
> > > > if ((prog->type == BPF_PROG_TYPE_TRACING ||
> > > > prog->type == BPF_PROG_TYPE_LSM ||
> > > > prog->type == BPF_PROG_TYPE_EXT) && !prog->attach_btf_id) {
> > > > @@ -8600,8 +8603,11 @@ static const struct bpf_sec_def section_defs[] = {
> > > > SEC_DEF("lsm.s/", LSM, BPF_LSM_MAC, SEC_ATTACH_BTF | SEC_SLEEPABLE, attach_lsm),
> > > > SEC_DEF("iter/", TRACING, BPF_TRACE_ITER, SEC_ATTACH_BTF, attach_iter),
> > > > SEC_DEF("syscall", SYSCALL, 0, SEC_SLEEPABLE),
> > > > + SEC_DEF("xdp.frags/devmap", XDP, BPF_XDP_DEVMAP, SEC_NONE),
> > > > SEC_DEF("xdp_devmap/", XDP, BPF_XDP_DEVMAP, SEC_ATTACHABLE),
> > > > + SEC_DEF("xdp.frags/cpumap", XDP, BPF_XDP_CPUMAP, SEC_NONE),
> > > > SEC_DEF("xdp_cpumap/", XDP, BPF_XDP_CPUMAP, SEC_ATTACHABLE),
> > > > + SEC_DEF("xdp.frags", XDP, BPF_XDP, SEC_NONE),
> > >
> > > It would be SEC_FRAGS here instead of SEC_NONE.
> >
> > ack, I dropped SEC_FRAGS (SEC_XDP_MB before) from sec_def_flags because Andrii asked to remove
> > it but I am fine to add it back. Agree?
>
> Andrii,
> what was the motivation?
> imo that's cleaner than strstr.
Given it was XDP-specific (as opposed to sleepable flag that applies
more widely), it felt cleaner ([0]) to handle that as a special case
in libbpf_preload_prog. But I didn't feel that strongly about that
back then and still don't, so if you think SEC_FRAGS is better, I'm
fine with it. I'd make it SEC_XDP_FRAGS to make it more obvious it's
still XDP-specific (there are no plans to extend it to non-XDP,
right?).
But whichever way, it's internal implementation detail and pretty
small one at that, so I don't care much.
[0] https://lore.kernel.org/bpf/CAEf4BzbfDvH5CYNsWg9Dx7JcFEp4jNmNRR6H-6sJEUxDSy1zZw@mail.gmail.com/
next prev parent reply other threads:[~2022-01-19 1:11 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-17 17:28 [PATCH v22 bpf-next 00/23] mvneta: introduce XDP multi-buffer support Lorenzo Bianconi
2022-01-17 17:28 ` [PATCH v22 bpf-next 01/23] net: skbuff: add size metadata to skb_shared_info for xdp Lorenzo Bianconi
2022-01-17 17:28 ` [PATCH v22 bpf-next 02/23] xdp: introduce flags field in xdp_buff/xdp_frame Lorenzo Bianconi
2022-01-17 17:28 ` [PATCH v22 bpf-next 03/23] net: mvneta: update multi-frags bit before passing the xdp buffer to eBPF layer Lorenzo Bianconi
2022-01-17 17:28 ` [PATCH v22 bpf-next 04/23] net: mvneta: simplify mvneta_swbm_add_rx_fragment management Lorenzo Bianconi
2022-01-17 17:28 ` [PATCH v22 bpf-next 05/23] net: xdp: add xdp_update_skb_shared_info utility routine Lorenzo Bianconi
2022-01-17 17:28 ` [PATCH v22 bpf-next 06/23] net: marvell: rely on " Lorenzo Bianconi
2022-01-17 17:28 ` [PATCH v22 bpf-next 07/23] xdp: add multi-frags support to xdp_return_{buff/frame} Lorenzo Bianconi
2022-01-17 17:28 ` [PATCH v22 bpf-next 08/23] net: mvneta: add multi-frags support to XDP_TX Lorenzo Bianconi
2022-01-17 17:28 ` [PATCH v22 bpf-next 09/23] bpf: introduce BPF_F_XDP_HAS_FRAGS flag in prog_flags loading the ebpf program Lorenzo Bianconi
2022-01-17 17:28 ` [PATCH v22 bpf-next 10/23] net: mvneta: enable jumbo frames if the loaded XDP program support multi-frags Lorenzo Bianconi
2022-01-17 17:28 ` [PATCH v22 bpf-next 11/23] bpf: introduce bpf_xdp_get_buff_len helper Lorenzo Bianconi
2022-01-17 17:28 ` [PATCH v22 bpf-next 12/23] bpf: add multi-frags support to the bpf_xdp_adjust_tail() API Lorenzo Bianconi
2022-01-18 20:20 ` Alexei Starovoitov
2022-01-18 22:25 ` Lorenzo Bianconi
2022-01-17 17:28 ` [PATCH v22 bpf-next 13/23] bpf: add multi-frags support to xdp copy helpers Lorenzo Bianconi
2022-01-17 17:28 ` [PATCH v22 bpf-next 14/23] bpf: move user_size out of bpf_test_init Lorenzo Bianconi
2022-01-17 17:28 ` [PATCH v22 bpf-next 15/23] bpf: introduce multi-frags support to bpf_prog_test_run_xdp() Lorenzo Bianconi
2022-01-17 17:28 ` [PATCH v22 bpf-next 16/23] bpf: test_run: add xdp_shared_info pointer in bpf_test_finish signature Lorenzo Bianconi
2022-01-17 17:28 ` [PATCH v22 bpf-next 17/23] bpf: selftests: update xdp_adjust_tail selftest to include multi-frags Lorenzo Bianconi
2022-01-18 20:16 ` Alexei Starovoitov
2022-01-18 22:23 ` Lorenzo Bianconi
2022-01-18 22:30 ` Alexei Starovoitov
2022-01-17 17:28 ` [PATCH v22 bpf-next 18/23] libbpf: Add SEC name for xdp multi-frags programs Lorenzo Bianconi
2022-01-18 20:14 ` Alexei Starovoitov
2022-01-18 22:31 ` Lorenzo Bianconi
2022-01-18 22:33 ` Alexei Starovoitov
2022-01-19 1:11 ` Andrii Nakryiko [this message]
2022-01-19 9:38 ` Lorenzo Bianconi
2022-01-17 17:28 ` [PATCH v22 bpf-next 19/23] bpf: generalise tail call map compatibility check Lorenzo Bianconi
2022-01-18 20:23 ` Alexei Starovoitov
2022-01-18 22:13 ` Lorenzo Bianconi
2022-01-17 17:28 ` [PATCH v22 bpf-next 20/23] net: xdp: introduce bpf_xdp_pointer utility routine Lorenzo Bianconi
2022-01-17 17:28 ` [PATCH v22 bpf-next 21/23] bpf: selftests: introduce bpf_xdp_{load,store}_bytes selftest Lorenzo Bianconi
2022-01-17 17:28 ` [PATCH v22 bpf-next 22/23] bpf: selftests: add CPUMAP/DEVMAP selftests for xdp multi-frags Lorenzo Bianconi
2022-01-17 17:28 ` [PATCH v22 bpf-next 23/23] xdp: disable XDP_REDIRECT " 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=CAEf4BzYHyCz5QNwuuKnRRrqCTcP0c0Q6fdi0N5_Yp8yNXvxReQ@mail.gmail.com \
--to=andrii.nakryiko@gmail.com \
--cc=alexander.duyck@gmail.com \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=brouer@redhat.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=echaudro@redhat.com \
--cc=jasowang@redhat.com \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=lorenzo.bianconi@redhat.com \
--cc=lorenzo@kernel.org \
--cc=maciej.fijalkowski@intel.com \
--cc=magnus.karlsson@intel.com \
--cc=netdev@vger.kernel.org \
--cc=saeed@kernel.org \
--cc=shayagr@amazon.com \
--cc=tirthendu.sarkar@intel.com \
--cc=toke@redhat.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).