[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id:
<176280541325.2759707.7993878047530807107.git-patchwork-notify@kernel.org>
Date: Mon, 10 Nov 2025 20:10:13 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: D. Wythe <alibuda@...ux.alibaba.com>
Cc: ast@...nel.org, daniel@...earbox.net, andrii@...nel.org,
martin.lau@...ux.dev, pabeni@...hat.com, song@...nel.org, sdf@...gle.com,
haoluo@...gle.com, yhs@...com, edumazet@...gle.com, john.fastabend@...il.com,
kpsingh@...nel.org, jolsa@...nel.org, mjambigi@...ux.ibm.com,
wenjia@...ux.ibm.com, wintera@...ux.ibm.com, dust.li@...ux.alibaba.com,
tonylu@...ux.alibaba.com, guwen@...ux.alibaba.com, bpf@...r.kernel.org,
davem@...emloft.net, kuba@...nel.org, netdev@...r.kernel.org,
sidraya@...ux.ibm.com, jaka@...ux.ibm.com
Subject: Re: [PATCH bpf-next v5 0/3] net/smc: Introduce smc_hs_ctrl
Hello:
This series was applied to bpf/bpf-next.git (net)
by Martin KaFai Lau <martin.lau@...nel.org>:
On Fri, 7 Nov 2025 11:56:29 +0800 you wrote:
> This patch aims to introduce BPF injection capabilities for SMC and
> includes a self-test to ensure code stability.
>
> Since the SMC protocol isn't ideal for every situation, especially
> short-lived ones, most applications can't guarantee the absence of
> such scenarios. Consequently, applications may need specific strategies
> to decide whether to use SMC. For example, an application might limit SMC
> usage to certain IP addresses or ports.
>
> [...]
Here is the summary with links:
- [bpf-next,v5,1/3] bpf: export necessary symbols for modules with struct_ops
https://git.kernel.org/bpf/bpf-next/c/07c428ece322
- [bpf-next,v5,2/3] net/smc: bpf: Introduce generic hook for handshake flow
https://git.kernel.org/bpf/bpf-next/c/15f295f55656
- [bpf-next,v5,3/3] bpf/selftests: add selftest for bpf_smc_hs_ctrl
https://git.kernel.org/bpf/bpf-next/c/beb3c67297d9
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists