Skip to content

RFC net/smc: Introduce BPF injection capability

D. Wythe bpf linux-rdma linux-s390 llvm netdev oe-kbuild-all 1 version In review

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 RFC Latest5 patches 1 replyIn review

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/5net/smc: move smc_sock related structure definitioninclude/net/smc.h net/smc/smc.h+225 -2240 replies
2/5net/smc: net/smc: allow smc to negotiate protocols on policiesinclude/net/smc.h net/Makefile net/smc/Kconfig +2 more+324 -10 replies
3/5net/smc: allow set or get smc negotiator by sockoptinclude/uapi/linux/smc.h net/smc/af_smc.c+102 -340 replies
4/5bpf: add smc negotiator support in BPF struct_opskernel/bpf/bpf_struct_ops_types.h net/smc/bpf_smc.c+163 -00 replies
5/5bpf/selftests: add selftest for SMC bpf capabilitytools/testing/selftests/bpf/prog_tests/bpf_smc.c tools/testing/selftests/bpf/progs/bpf_smc.c+372 -00 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [RFC PATCH bpf-next 0/5] net/smc: Introduce BPF injection capability

From: "D. Wythe" <[email protected]>

This patches attempt to introduce BPF injection capability for SMC, and add selftest to ensure code stability.

As we all know that the SMC protocol is not suitable for all scenarios, especially for short-lived. However, for most applications, they cannot guarantee that there are no such scenarios at all. Therefore, apps may need some specific strategies to decide shall we need to use SMC or not, for example, apps can limit the scope of the SMC to a specific IP address or port.

Based on the consideration of transparent replacement, we hope that apps can remain transparent even if they need to formulate some specific strategies for SMC using. That is, do not need to recompile their code.

On the other hand, we need to ensure the scalability of strategies implementation. Although it is simple to use socket options or sysctl, it will bring more complexity to subsequent expansion.

Fortunately, BPF can solve these concerns very well, users can write thire own strategies in eBPF to choose whether to use SMC or not. And it's quite easy for them to modify their strategies in the future.

This patches implement injection capability for SMC via struct_ops. In that way, we can add new injection scenarios in the future.

D. Wythe (5):
net/smc: move smc_sock related structure definition net/smc: net/smc: allow smc to negotiate protocols on policies net/smc: allow set or get smc negotiator by sockopt
bpf: add smc negotiator support in BPF struct_ops bpf/selftests: add selftest for SMC bpf capability

 include/net/smc.h                                | 268 +++++++++++++++++
 include/uapi/linux/smc.h                         |   1 +
 kernel/bpf/bpf_struct_ops_types.h                |   4 +
 net/Makefile                                     |   1 +
 net/smc/Kconfig                                  |  13 +
 net/smc/af_smc.c                                 | 203 ++++++++++---
 net/smc/bpf_smc.c                                | 359 +++++++++++++++++++++++
 net/smc/smc.h                                    | 224 --------------
 tools/testing/selftests/bpf/prog_tests/bpf_smc.c | 107 +++++++
 tools/testing/selftests/bpf/progs/bpf_smc.c      | 265 +++++++++++++++++
 10 files changed, 1186 insertions(+), 259 deletions(-)
 create mode 100644 net/smc/bpf_smc.c
 create mode 100644 tools/testing/selftests/bpf/prog_tests/bpf_smc.c
 create mode 100644 tools/testing/selftests/bpf/progs/bpf_smc.c
Signature · 1 line
1.8.3.1