[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1729737768-124596-1-git-send-email-alibuda@linux.alibaba.com>
Date: Thu, 24 Oct 2024 10:42:44 +0800
From: "D. Wythe" <alibuda@...ux.alibaba.com>
To: kgraul@...ux.ibm.com,
wenjia@...ux.ibm.com,
jaka@...ux.ibm.com,
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,
guwen@...ux.alibaba.com
Cc: kuba@...nel.org,
davem@...emloft.net,
netdev@...r.kernel.org,
linux-s390@...r.kernel.org,
linux-rdma@...r.kernel.org,
bpf@...r.kernel.org,
dtcccc@...ux.alibaba.com
Subject: [PATCH bpf-next 0/4] net/smc: Introduce smc_bpf_ops
From: "D. Wythe" <alibuda@...ux.alibaba.com>
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 (4):
bpf: export necessary sympols for modules
bpf: allow to access bpf_prog during bpf_struct_access
net/smc: Introduce smc_bpf_ops
bpf/selftests: add simple selftest for bpf_smc_ops
include/linux/bpf.h | 1 +
include/linux/filter.h | 1 +
include/linux/tcp.h | 2 +-
include/net/smc.h | 47 +++++
include/net/tcp.h | 6 +
kernel/bpf/btf.c | 2 +
kernel/bpf/verifier.c | 2 +-
kernel/sched/ext.c | 5 +-
net/bpf/bpf_dummy_struct_ops.c | 1 +
net/core/filter.c | 7 +-
net/ipv4/bpf_tcp_ca.c | 1 +
net/ipv4/tcp_input.c | 3 +-
net/ipv4/tcp_output.c | 14 +-
net/netfilter/nf_conntrack_bpf.c | 1 +
net/smc/Kconfig | 12 ++
net/smc/Makefile | 1 +
net/smc/af_smc.c | 38 +++-
net/smc/smc.h | 4 +
net/smc/smc_bpf.c | 212 +++++++++++++++++++++
net/smc/smc_bpf.h | 34 ++++
.../selftests/bpf/bpf_testmod/bpf_testmod.c | 1 +
.../selftests/bpf/prog_tests/test_bpf_smc.c | 21 ++
tools/testing/selftests/bpf/progs/bpf_smc.c | 44 +++++
23 files changed, 439 insertions(+), 21 deletions(-)
create mode 100644 net/smc/smc_bpf.c
create mode 100644 net/smc/smc_bpf.h
create mode 100644 tools/testing/selftests/bpf/prog_tests/test_bpf_smc.c
create mode 100644 tools/testing/selftests/bpf/progs/bpf_smc.c
--
1.8.3.1
Powered by blists - more mailing lists