From: "D. Wythe" <alibuda@linux.alibaba.com>
To: kgraul@linux.ibm.com, wenjia@linux.ibm.com, jaka@linux.ibm.com,
ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org
Cc: kuba@kernel.org, davem@davemloft.net, netdev@vger.kernel.org,
linux-s390@vger.kernel.org, linux-rdma@vger.kernel.org,
bpf@vger.kernel.org
Subject: [PATCH bpf-next v2 0/2] net/smc: Introduce BPF injection capability
Date: Tue, 21 Feb 2023 20:18:37 +0800 [thread overview]
Message-ID: <1676981919-64884-1-git-send-email-alibuda@linux.alibaba.com> (raw)
From: "D. Wythe" <alibuda@linux.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 (2):
net/smc: Introduce BPF injection capability for SMC
bpf/selftests: Test for SMC protocol negotiate
include/linux/btf_ids.h | 15 ++
include/net/smc.h | 254 ++++++++++++++++++
kernel/bpf/bpf_struct_ops_types.h | 4 +
net/Makefile | 5 +
net/smc/af_smc.c | 10 +-
net/smc/bpf_smc_struct_ops.c | 146 +++++++++++
net/smc/smc.h | 220 ----------------
tools/testing/selftests/bpf/prog_tests/bpf_smc.c | 39 +++
tools/testing/selftests/bpf/progs/bpf_smc.c | 315 +++++++++++++++++++++++
9 files changed, 787 insertions(+), 221 deletions(-)
create mode 100644 net/smc/bpf_smc_struct_ops.c
create mode 100644 tools/testing/selftests/bpf/prog_tests/bpf_smc.c
create mode 100644 tools/testing/selftests/bpf/progs/bpf_smc.c
--
1.8.3.1
next reply other threads:[~2023-02-21 12:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-21 12:18 D. Wythe [this message]
2023-02-21 12:18 ` [PATCH bpf-next v2 1/2] net/smc: Introduce BPF injection capability for SMC D. Wythe
2023-02-22 21:40 ` Martin KaFai Lau
2023-03-09 11:49 ` D. Wythe
2023-03-23 20:46 ` Martin KaFai Lau
2023-03-24 4:08 ` D. Wythe
2023-03-24 23:27 ` Martin KaFai Lau
2023-04-03 8:21 ` D. Wythe
2023-02-27 7:58 ` Wenjia Zhang
2023-02-28 8:50 ` D. Wythe
2023-02-28 8:58 ` Wenjia Zhang
2023-02-21 12:18 ` [PATCH bpf-next v2 2/2] bpf/selftests: add selftest for SMC bpf capability D. Wythe
2023-02-22 22:35 ` Martin KaFai Lau
2023-03-09 11:58 ` 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=1676981919-64884-1-git-send-email-alibuda@linux.alibaba.com \
--to=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=jaka@linux.ibm.com \
--cc=kgraul@linux.ibm.com \
--cc=kuba@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=wenjia@linux.ibm.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;
as well as URLs for NNTP newsgroup(s).