From: "Alexei Starovoitov" <alexei.starovoitov@gmail.com>
To: "ThisSeanZhang" <thisseanzhang@gmail.com>, <bpf@vger.kernel.org>
Cc: "Alexei Starovoitov" <ast@kernel.org>,
"Daniel Borkmann" <daniel@iogearbox.net>,
"Andrii Nakryiko" <andrii@kernel.org>,
"Eduard Zingerman" <eddyz87@gmail.com>, <netdev@vger.kernel.org>,
"Nick Hudson" <nhudson@akamai.com>,
"Felix Fietkau" <nbd@openwrt.org>,
"Qingfang Deng" <dqfext@gmail.com>
Subject: Re: [RFC bpf-next 0/3] bpf: Add PPPoE encap/decap support to bpf_skb_adjust_room
Date: Sun, 27 Sep 2026 04:41:41 +0000 [thread overview]
Message-ID: <DLPTN52TGGMY.TPWL2GZA38RK@gmail.com> (raw)
In-Reply-To: <20260926210757.2152159-1-thisseanzhang@gmail.com>
On Sat Sep 26, 2026 at 9:07 PM UTC, ThisSeanZhang wrote:
> Hello,
>
> This series adds PPPoE session encapsulation and decapsulation support to
> bpf_skb_adjust_room(), allowing TC BPF programs to update packet data and
> skb metadata consistently.
Why?
Is this a research project on what llm can implement?
It certainly can, but it's not a reason to add new uapi.
pw-bot: cr
next prev parent reply other threads:[~2026-09-27 4:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-26 21:07 [RFC bpf-next 0/3] bpf: Add PPPoE encap/decap support to bpf_skb_adjust_room ThisSeanZhang
2026-09-26 21:07 ` [RFC bpf-next 1/3] bpf: Add PPPoE encap " ThisSeanZhang
2026-09-26 21:07 ` [RFC bpf-next 2/3] bpf: Add PPPoE decap " ThisSeanZhang
2026-09-26 21:07 ` [RFC bpf-next 3/3] selftests/bpf: Add a test for the PPPoE encap/decap adjust_room flags ThisSeanZhang
2026-09-27 4:41 ` Alexei Starovoitov [this message]
2026-09-27 6:13 ` [RFC bpf-next 0/3] bpf: Add PPPoE encap/decap support to bpf_skb_adjust_room Sean zhang
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=DLPTN52TGGMY.TPWL2GZA38RK@gmail.com \
--to=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=dqfext@gmail.com \
--cc=eddyz87@gmail.com \
--cc=nbd@openwrt.org \
--cc=netdev@vger.kernel.org \
--cc=nhudson@akamai.com \
--cc=thisseanzhang@gmail.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