From: Martin KaFai Lau <martin.lau@linux.dev>
To: "D. Wythe" <alibuda@linux.alibaba.com>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
pabeni@redhat.com, song@kernel.org, sdf@google.com,
haoluo@google.com, yhs@fb.com, edumazet@google.com,
john.fastabend@gmail.com, kpsingh@kernel.org, jolsa@kernel.org,
mjambigi@linux.ibm.com, wenjia@linux.ibm.com,
wintera@linux.ibm.com, dust.li@linux.alibaba.com,
tonylu@linux.alibaba.com, guwen@linux.alibaba.com,
bpf@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
netdev@vger.kernel.org, sidraya@linux.ibm.com,
jaka@linux.ibm.com
Subject: Re: [PATCH bpf-next v4 2/3] net/smc: bpf: Introduce generic hook for handshake flow
Date: Tue, 4 Nov 2025 16:03:46 -0800 [thread overview]
Message-ID: <4450b847-6b31-46f2-bc2d-a8b3197d15c7@linux.dev> (raw)
In-Reply-To: <20251103073124.43077-3-alibuda@linux.alibaba.com>
On 11/2/25 11:31 PM, D. Wythe wrote:
> +#if IS_ENABLED(CONFIG_SMC_HS_CTRL_BPF)
> +#define smc_call_hsbpf(init_val, sk, func, ...) ({ \
> + typeof(init_val) __ret = (init_val); \
> + struct smc_hs_ctrl *ctrl; \
> + rcu_read_lock(); \
> + ctrl = rcu_dereference(sock_net(sk)->smc.hs_ctrl); \
The smc_hs_ctrl (and its ops) is called from the netns, so the
bpf_struct_ops is attached to a netns. Attaching bpf_struct_ops to a
netns has not been done before. More on this later.
> + if (ctrl && ctrl->func) \
> + __ret = ctrl->func(__VA_ARGS__); \
> + rcu_read_unlock(); \
> + __ret; \
> +})
> +#else
> +#define smc_call_hsbpf(init_val, sk, ...) ({ (void)(sk); (init_val); })
> +#endif /* CONFIG_SMC_HS_CTRL_BPF */
> +
> #endif /* _SMC_H */
> diff --git a/net/ipv4/tcp_output.c b/net/ipv4/tcp_output.c
> index 7f5df7a71f62..1a3234729a29 100644
> --- a/net/ipv4/tcp_output.c
> +++ b/net/ipv4/tcp_output.c
> @@ -40,6 +40,7 @@
> #include <net/tcp.h>
> #include <net/tcp_ecn.h>
> #include <net/mptcp.h>
> +#include <net/smc.h>
> #include <net/proto_memory.h>
> #include <net/psp.h>
>
> @@ -802,34 +803,41 @@ static void tcp_options_write(struct tcphdr *th, struct tcp_sock *tp,
> mptcp_options_write(th, ptr, tp, opts);
> }
>
> -static void smc_set_option(const struct tcp_sock *tp,
> +static void smc_set_option(struct tcp_sock *tp,
> struct tcp_out_options *opts,
> unsigned int *remaining)
> {
> #if IS_ENABLED(CONFIG_SMC)
> - if (static_branch_unlikely(&tcp_have_smc)) {
> - if (tp->syn_smc) {
> - if (*remaining >= TCPOLEN_EXP_SMC_BASE_ALIGNED) {
> - opts->options |= OPTION_SMC;
> - *remaining -= TCPOLEN_EXP_SMC_BASE_ALIGNED;
> - }
> + struct sock *sk = &tp->inet_conn.icsk_inet.sk;
the sk is tp ...
> +
> + if (static_branch_unlikely(&tcp_have_smc) && tp->syn_smc) {
> + tp->syn_smc = !!smc_call_hsbpf(1, sk, syn_option, tp);
... so just pass tp instead of passing both sk and tp?
[ ... ]
> +static int smc_bpf_hs_ctrl_init(struct btf *btf) { return 0; }
> +
> +static int smc_bpf_hs_ctrl_reg(void *kdata, struct bpf_link *link)
More on attaching to netns. There is discussion on how to attach a
bpf_struct_ops to a particular cgroup in a link. I think the link should
be able to attach a bpf_struct_ops to a particular netns also.
I would suggest to reject link now. Later, link support can be added to
attach to a particular netns. This will be the last non-link-only
bpf_struct_ops addition, considering the blast radius is limited on
smc_hs_ctrl and the smc effort was started a while ago. I could have
missed things here. Other experts could chime in.
if (link)
return -EOPNOTSUPP;
pw-bot: cr
> +{
> + return smc_hs_ctrl_reg(kdata);
> +}
> +
> +static void smc_bpf_hs_ctrl_unreg(void *kdata, struct bpf_link *link)
> +{
> + smc_hs_ctrl_unreg(kdata);
> +}
> +
next prev parent reply other threads:[~2025-11-05 0:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-03 7:31 [PATCH bpf-next v4 0/3] net/smc: Introduce smc_hs_ctrl D. Wythe
2025-11-03 7:31 ` [PATCH bpf-next v4 1/3] bpf: export necessary symbols for modules with struct_ops D. Wythe
2025-11-03 7:31 ` [PATCH bpf-next v4 2/3] net/smc: bpf: Introduce generic hook for handshake flow D. Wythe
2025-11-03 7:55 ` bot+bpf-ci
2025-11-03 9:18 ` D. Wythe
2025-11-05 0:03 ` Martin KaFai Lau [this message]
2025-11-05 7:01 ` D. Wythe
2025-11-05 22:58 ` Martin KaFai Lau
2025-11-06 2:33 ` D. Wythe
2025-11-06 4:16 ` Martin KaFai Lau
2025-11-06 8:34 ` D. Wythe
2025-11-06 17:15 ` Martin KaFai Lau
2025-11-07 3:11 ` D. Wythe
2025-11-03 7:31 ` [PATCH bpf-next v4 3/3] bpf/selftests: add selftest for bpf_smc_hs_ctrl D. Wythe
2025-11-05 0:13 ` Martin KaFai Lau
2025-11-05 7:04 ` D. Wythe
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=4450b847-6b31-46f2-bc2d-a8b3197d15c7@linux.dev \
--to=martin.lau@linux.dev \
--cc=alibuda@linux.alibaba.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=dust.li@linux.alibaba.com \
--cc=edumazet@google.com \
--cc=guwen@linux.alibaba.com \
--cc=haoluo@google.com \
--cc=jaka@linux.ibm.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=kuba@kernel.org \
--cc=mjambigi@linux.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@google.com \
--cc=sidraya@linux.ibm.com \
--cc=song@kernel.org \
--cc=tonylu@linux.alibaba.com \
--cc=wenjia@linux.ibm.com \
--cc=wintera@linux.ibm.com \
--cc=yhs@fb.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