| Message ID | 1676964305-1093-1-git-send-email-alibuda@linux.alibaba.com (mailing list archive) |
|---|---|
| Headers | show |
| Series | net/smc: Introduce BPF injection capability | expand |
Sorry for forgot to cc the maintainer of BPF, please ignore this. I will resend a new version. On 2/21/23 3:25 PM, D. Wythe wrote: > From: "D. Wythe" <alibuda@linux.alibaba.com> > > This PATCHes attempts 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 > net/smc: add selftest for SMC bpf capability > > 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 >
On Tue, Feb 21, 2023 at 03:29:59PM +0800, D. Wythe wrote: > > Sorry for forgot to cc the maintainer of BPF, > please ignore this. I will resend a new version. net-next is closed. You'll need to repost it, either as an RFC, or wait until after v6.3-rc1 has been tagged.
On 2/22/23 12:25 AM, Simon Horman wrote: > On Tue, Feb 21, 2023 at 03:29:59PM +0800, D. Wythe wrote: >> >> Sorry for forgot to cc the maintainer of BPF, >> please ignore this. I will resend a new version. > > net-next is closed. > > You'll need to repost it, either as an RFC, or wait until after > v6.3-rc1 has been tagged. I had repost it to bpf-next, but thank you for your reminding! Best wishes. D. Wythe
On Wed, Feb 22, 2023 at 10:37:28AM +0800, D. Wythe wrote: > > > On 2/22/23 12:25 AM, Simon Horman wrote: > > On Tue, Feb 21, 2023 at 03:29:59PM +0800, D. Wythe wrote: > > > > > > Sorry for forgot to cc the maintainer of BPF, > > > please ignore this. I will resend a new version. > > > > net-next is closed. > > > > You'll need to repost it, either as an RFC, or wait until after > > v6.3-rc1 has been tagged. > > I had repost it to bpf-next, but thank you for your reminding! Sorry, my mistake.
From: "D. Wythe" <alibuda@linux.alibaba.com> This PATCHes attempts 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 net/smc: add selftest for SMC bpf capability 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