From: Jakub Kicinski <kuba@kernel.org>
To: Vincent Whitchurch via B4 Relay
<devnull+vincent.whitchurch.datadoghq.com@kernel.org>
Cc: vincent.whitchurch@datadoghq.com,
John Fastabend <john.fastabend@gmail.com>,
Jakub Sitnicki <jakub@cloudflare.com>,
Kuniyuki Iwashima <kuniyu@amazon.com>,
netdev@vger.kernel.org, bpf@vger.kernel.org
Subject: Re: [PATCH bpf-next v2 1/5] net: Add splice_read to prot
Date: Mon, 9 Jun 2025 12:21:46 -0700 [thread overview]
Message-ID: <20250609122146.3e92eaef@kernel.org> (raw)
In-Reply-To: <20250609-sockmap-splice-v2-1-9c50645cfa32@datadoghq.com>
On Mon, 09 Jun 2025 15:26:58 +0200 Vincent Whitchurch via B4 Relay
wrote:
> The TCP BPF code will need to override splice_read(), so add it to prot.
Can we not override proto_ops in tcp_bpf for some specific reason?
TLS does that, IIUC.
next prev parent reply other threads:[~2025-06-09 19:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-09 13:26 [PATCH bpf-next v2 0/5] sockmap: Fix reading with splice(2) Vincent Whitchurch via B4 Relay
2025-06-09 13:26 ` Vincent Whitchurch
2025-06-09 13:26 ` [PATCH bpf-next v2 1/5] net: Add splice_read to prot Vincent Whitchurch via B4 Relay
2025-06-09 13:26 ` Vincent Whitchurch
2025-06-09 19:21 ` Jakub Kicinski [this message]
2025-06-11 8:57 ` Vincent Whitchurch
2025-06-20 15:44 ` Vincent Whitchurch
2025-06-09 13:26 ` [PATCH bpf-next v2 2/5] tcp_bpf: Fix reading with splice(2) Vincent Whitchurch via B4 Relay
2025-06-09 13:26 ` Vincent Whitchurch
2025-06-09 13:27 ` [PATCH bpf-next v2 3/5] selftests/bpf: sockmap: Exit with error on failure Vincent Whitchurch via B4 Relay
2025-06-09 13:27 ` Vincent Whitchurch
2025-06-09 13:27 ` [PATCH bpf-next v2 4/5] selftests/bpf: sockmap: Allow SK_PASS in verdict Vincent Whitchurch via B4 Relay
2025-06-09 13:27 ` Vincent Whitchurch
2025-06-09 13:27 ` [PATCH bpf-next v2 5/5] selftests/bpf: sockmap: Add splice + SK_PASS regression test Vincent Whitchurch via B4 Relay
2025-06-09 13:27 ` Vincent Whitchurch
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=20250609122146.3e92eaef@kernel.org \
--to=kuba@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=devnull+vincent.whitchurch.datadoghq.com@kernel.org \
--cc=jakub@cloudflare.com \
--cc=john.fastabend@gmail.com \
--cc=kuniyu@amazon.com \
--cc=netdev@vger.kernel.org \
--cc=vincent.whitchurch@datadoghq.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.