From: Jakub Kicinski <kuba@kernel.org>
To: Jakub Sitnicki <jakub@cloudflare.com>, Paolo Abeni <pabeni@redhat.com>
Cc: Alexei Starovoitov <alexei.starovoitov@gmail.com>,
bpf <bpf@vger.kernel.org>,
Martin KaFai Lau <martin.lau@linux.dev>,
Network Development <netdev@vger.kernel.org>,
kernel-team <kernel-team@cloudflare.com>
Subject: Re: [PATCH RFC bpf-next 0/5] skb extension for BPF local storage
Date: Sat, 28 Feb 2026 15:50:21 -0800 [thread overview]
Message-ID: <20260228155021.1dc9b127@kernel.org> (raw)
In-Reply-To: <87wlzydk12.fsf@cloudflare.com>
On Fri, 27 Feb 2026 21:11:05 +0100 Jakub Sitnicki wrote:
> So to exhaust all alternatives I gotta ask - would you and Jakub be open
> to the idea of a plain byte buffer embedded in skb_ext and exposed as a
> bpf_dynptr?
I'm fine with that, but admittedly I (like you?) live in
the comfortable universe of controlling which .config options
are suitable for the narrow use cases I care about.
So I don't really trust my judgment. Adding Paolo..
next prev parent reply other threads:[~2026-02-28 23:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-26 21:12 [PATCH RFC bpf-next 0/5] skb extension for BPF local storage Jakub Sitnicki
2026-02-26 21:12 ` [PATCH RFC bpf-next 1/5] bpf: Introduce local storage for sk_buff Jakub Sitnicki
2026-02-26 21:12 ` [PATCH RFC bpf-next 2/5] bpf: Allow passing kernel context pointer to kfuncs Jakub Sitnicki
2026-02-26 21:12 ` [PATCH RFC bpf-next 3/5] bpf: Allow access to bpf_sock_ops_kern->skb Jakub Sitnicki
2026-02-26 21:12 ` [PATCH RFC bpf-next 4/5] selftests/bpf: Add verifier tests for skb local storage Jakub Sitnicki
2026-02-26 21:12 ` [PATCH RFC bpf-next 5/5] selftests/bpf: Add functional " Jakub Sitnicki
2026-02-26 21:56 ` [PATCH RFC bpf-next 0/5] skb extension for BPF " Alexei Starovoitov
2026-02-27 20:11 ` Jakub Sitnicki
2026-02-28 23:50 ` Jakub Kicinski [this message]
2026-03-01 17:59 ` Jakub Sitnicki
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=20260228155021.1dc9b127@kernel.org \
--to=kuba@kernel.org \
--cc=alexei.starovoitov@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=jakub@cloudflare.com \
--cc=kernel-team@cloudflare.com \
--cc=martin.lau@linux.dev \
--cc=netdev@vger.kernel.org \
--cc=pabeni@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