From: Jakub Kicinski <kuba@kernel.org>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: David Vernet <void@manifault.com>,
Andrii Nakryiko <andrii.nakryiko@gmail.com>,
Joanne Koong <joannelkoong@gmail.com>, bpf <bpf@vger.kernel.org>,
Andrii Nakryiko <andrii@kernel.org>,
kernel-team@meta.com, Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Martin KaFai Lau <martin.lau@linux.dev>,
Song Liu <song@kernel.org>
Subject: Re: bpf helpers freeze. Was: [PATCH v2 bpf-next 0/6] Dynptr convenience helpers
Date: Tue, 3 Jan 2023 16:55:50 -0800 [thread overview]
Message-ID: <20230103165550.56bf9717@kernel.org> (raw)
In-Reply-To: <20221231004213.h5fx3loccbs5hyzu@macbook-pro-6.dhcp.thefacebook.com>
On Fri, 30 Dec 2022 16:42:13 -0800 Alexei Starovoitov wrote:
> iirc Martin and Kuba had concerns about bits of dynptr(skb | xdp) too.
FWIW yes, I withdrew my objections because Joanne showed me some changes
which reduced LOC in user space even with the limited functionality.
But dynptrs are not the efficient skb/xdp buf abstraction I was hoping
for :(
next prev parent reply other threads:[~2023-01-04 0:56 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-07 20:55 [PATCH v2 bpf-next 0/6] Dynptr convenience helpers Joanne Koong
2022-12-07 20:55 ` [PATCH v2 bpf-next 1/6] bpf: Add bpf_dynptr_trim and bpf_dynptr_advance Joanne Koong
2022-12-07 20:55 ` [PATCH v2 bpf-next 2/6] bpf: Add bpf_dynptr_is_null and bpf_dynptr_is_rdonly Joanne Koong
2022-12-07 20:55 ` [PATCH v2 bpf-next 3/6] bpf: Add bpf_dynptr_get_size and bpf_dynptr_get_offset Joanne Koong
2022-12-07 20:55 ` [PATCH v2 bpf-next 4/6] bpf: Add bpf_dynptr_clone Joanne Koong
2022-12-07 20:55 ` [PATCH v2 bpf-next 5/6] bpf: Add bpf_dynptr_iterator Joanne Koong
2022-12-07 20:55 ` [PATCH v2 bpf-next 6/6] selftests/bpf: Tests for dynptr convenience helpers Joanne Koong
2022-12-08 1:54 ` [PATCH v2 bpf-next 0/6] Dynptr " Alexei Starovoitov
2022-12-09 0:42 ` Andrii Nakryiko
2022-12-09 1:30 ` Alexei Starovoitov
2022-12-09 22:24 ` Joanne Koong
2022-12-12 20:12 ` Andrii Nakryiko
2022-12-13 23:50 ` Joanne Koong
2022-12-14 0:57 ` Andrii Nakryiko
2022-12-14 21:25 ` Joanne Koong
2022-12-16 17:35 ` Alexei Starovoitov
2022-12-20 19:31 ` Andrii Nakryiko
2022-12-25 21:52 ` bpf helpers freeze. Was: " Alexei Starovoitov
2022-12-29 23:10 ` Andrii Nakryiko
2022-12-30 2:46 ` Alexei Starovoitov
2022-12-30 18:38 ` David Vernet
2022-12-30 19:31 ` Alexei Starovoitov
2022-12-30 21:00 ` David Vernet
2022-12-31 0:42 ` Alexei Starovoitov
2023-01-03 11:43 ` Daniel Borkmann
2023-01-03 23:51 ` Alexei Starovoitov
2023-01-04 14:25 ` Daniel Borkmann
2023-01-04 18:59 ` Andrii Nakryiko
2023-01-04 20:03 ` Alexei Starovoitov
2023-01-04 21:57 ` Andrii Nakryiko
2023-01-04 19:37 ` Alexei Starovoitov
2023-01-05 0:13 ` Martin KaFai Lau
2023-01-05 17:17 ` KP Singh
2023-01-05 21:03 ` Andrii Nakryiko
2023-01-06 1:32 ` KP Singh
2023-01-05 21:02 ` Andrii Nakryiko
2023-01-04 20:50 ` David Vernet
2023-01-11 22:56 ` Maxim Mikityanskiy
2023-01-12 4:48 ` Alexei Starovoitov
2023-01-13 9:48 ` Jose E. Marchesi
2023-01-13 16:35 ` Alexei Starovoitov
2023-01-04 0:55 ` Jakub Kicinski [this message]
2023-01-04 18:44 ` Andrii Nakryiko
2023-01-04 19:56 ` Alexei Starovoitov
2023-01-04 18:43 ` Andrii Nakryiko
2023-01-04 19:51 ` Alexei Starovoitov
2023-01-04 21:56 ` Andrii Nakryiko
2023-01-04 18:43 ` Andrii Nakryiko
2023-01-04 19:44 ` Alexei Starovoitov
2023-01-04 21:55 ` Andrii Nakryiko
2023-01-04 23:47 ` David Vernet
2023-01-05 21:01 ` Andrii Nakryiko
2023-01-06 2:54 ` Alexei Starovoitov
2023-01-09 17:46 ` Andrii Nakryiko
2023-01-11 21:29 ` Song Liu
2023-01-12 4:23 ` Alexei Starovoitov
2023-01-12 7:35 ` Song Liu
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=20230103165550.56bf9717@kernel.org \
--to=kuba@kernel.org \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii.nakryiko@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=joannelkoong@gmail.com \
--cc=kernel-team@meta.com \
--cc=martin.lau@linux.dev \
--cc=song@kernel.org \
--cc=void@manifault.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